Git improvement #824
Git improvement #824
Conversation
|
@microsoft-github-policy-service agree |
|
Thanks @lucifertrj for the suggestions! We currently have an open PR to also add git log to this lesson, #782. I am waiting to hear back on that PR first. |
|
This PR has not seen any action for a while! Closing for now, but it can be reopened at a later date. |
There was a problem hiding this comment.
Thank you for the suggested changes @lucifertrj! I made a comment on the moving of the git log block. Will leave this PR open for you to resolve that item, once complete we can get the changeset merged in.
|
|
||
| ```bash | ||
| git commit -m "first commit" | ||
| ``` | ||
|
|
||
| This commits all of your files, adding the message "first commit". For future commit messages you will want to be more descriptive in your description to convey what type of change you've made. | ||
|
|
||
| 1. **Keep track of commits**. In the real-world applications we will most often deal with mutliple commit. In order to keep track of the commit history git provides `git log` command. |
There was a problem hiding this comment.
git log is a great addition to this lesson! There is an issue currently open (#1108) to include this within Task 2 of this lesson. If you'd like, for this PR, this block could be moved to match what is needed for that issue, or remove this block from your PR and it can be added separately.
saragibby
added
changes requested
Update README with
git logdetails and alternative forgit switch