Skip to content
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

Add examples from the common screwups resource in #40 #175

Merged
merged 2 commits into from
Dec 20, 2017

Conversation

RichardLitt
Copy link
Collaborator

This should close #40.

Copy link
Owner

@k88hudson k88hudson left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me! Thanks

README.md Outdated
If you want to see a file at a specific commit, you can also do this:

```sh
$ git show commitid:filename
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I know we have a lot of ways of representing "a commit id" but personally I prefer something a little more distinguishable from an actual command (like HASH1234 or b7c028) or explicit clarification in the description, i.e. you can also do this (where <commitid> is the commit you're interested in):

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is part of a larger issue. We should add a section at the top with conventions for the document, perhaps? For instance, we could use a nonce SHA (b7c028) throughout the document whenever we mean a commit id.

@RichardLitt RichardLitt force-pushed the feat/common-screwups-40 branch from 03af48e to a5d9903 Compare December 20, 2017 00:47
@RichardLitt RichardLitt merged commit f462bad into master Dec 20, 2017
aroup pushed a commit to aroup/git-flight-rules that referenced this pull request Jan 17, 2020
…dson#175)

* Adding submodule section

* Add the rest of the commands
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Resource: common git screwups and solutions post
2 participants