-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Trevor Community Contribution #17
base: main
Are you sure you want to change the base?
Conversation
I will put this on the github.md file instead |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A few minor edits, commit them as a batch and then link to this PR in your KWL repo to log the community badge
faq/github.md
Outdated
@@ -199,3 +199,18 @@ If you have trouble, create an issue and tag `@@rhodyprog4ds/fall20instructors` | |||
```` | |||
Doing each new assignment in its own branch is best practice. In a typical software development flow once the codebase is stable a new branch would be created for each new feature or patch. This analogy should help you build intuition for this GitHub flow and using branches. Also, pull requests are the best way for us to give you feedback. Also, if you create a branch when you do not need it, you can easily merge them after you are done, but it is hard to isolate things onto a branch if it's on main already. | |||
```` | |||
|
|||
## Why won't my experience badge workflow contain the new changes after I edit the workflow? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
## Why won't my experience badge workflow contain the new changes after I edit the workflow? | |
## Why did my workflow not run correctly? |
faq/github.md
Outdated
|
||
## Why won't my experience badge workflow contain the new changes after I edit the workflow? | ||
```{toggle} | ||
If you find that a workflow you may have made changes to are not properly reflecting your workflow changes is because you may not be running the workflow correctly. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If you find that a workflow you may have made changes to are not properly reflecting your workflow changes is because you may not be running the workflow correctly. | |
If you find that changes you made to a workflow are not taking effect, or you run a workflow and it seems to not work, you may not be running the workflow correctly. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I see the changes were made, but you did not use the PR review commit suggestion or add to batch options, how did you work on this?
I'm not completely familiar with batch options and I figured I could just copy and paste most of the changes into the clone I had open on vscode |
Actually completely ignore @brownsarahm. I was viewing the GitHub phone app before I even thought to check this PR to see the "add suggestion to batch option". I just saw it now looking over the PR and I will be sure to avoid making that mistake in the future. |
Not sure if this is where you wanted my faq addition. If not I can make a new file or whichever you think is the best option.