-
Notifications
You must be signed in to change notification settings - Fork 15
Git + GitHub additional skill #41
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
Conversation
c85fede to
bf816c1
Compare
| * Demonstrate setting the default upstream branch for a local branch | ||
| * Demonstrate force pushing rebases into isolated upstream Pull Request branches | ||
|
|
||
| ## GitHub |
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 couldn't think of anything else of interest on here. Maybe commenting?
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.
Demonstrate appropriate rebasing of isolated branches assuming this means rebasing/squashing commit history?
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.
yea
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.
Don't merge a branch with 50 commits
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.
Words to live by.
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.
Perhaps something around PR etiquette, but I don't really have anything to add. LGTM!
|
Git ignore missing |
|
Identifying files to ignore |
|
Etiquette around getting reviews / useful practices around leaving reviews |
|
Ensure all commits pass tests |
|
Seems more etiquette, not using git. Useful to know, but not core git? |
StevenLeighton21
left a comment
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.
General approval from me.
| ## Initializing | ||
|
|
||
| * Demonstrate initializing a new git repository | ||
| * Demonstrate creating an empty root commit |
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.
Had not thought about doing this, nice.
| * Demonstrate usage of `git status` | ||
| * Demonstrate staging files for commit | ||
| * Demonstrate committing staged files | ||
| * Demonstrate committing a subset of changed files using staged and unstaged files |
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.
How about staging only a subset of a file?
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.
Yeah I don’t do this
| * Demonstrate doing a simple rebase of master onto a branch | ||
| * Demonstrate performing an amend to previous commit | ||
| * Demonstrate performing an interactive rebase of a branch | ||
| * Demonstrate using all possible rebase options |
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.
Not sure what I’d be assessing here.
Scrap that I understand now, all the interactive rebase options.
|
Needs something about what a good commit message looks like. |
|
Going to merge and address commit messages in upcoming |
No description provided.