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

using git reset --hard origin/feature_branch #20

Open
pdurbin opened this issue Mar 15, 2013 · 2 comments
Open

using git reset --hard origin/feature_branch #20

pdurbin opened this issue Mar 15, 2013 · 2 comments

Comments

@pdurbin
Copy link

pdurbin commented Mar 15, 2013

At http://irclog.greptilian.com/sourcefu/2013-03-15 @ironcamel mentioned asking a collaborator use

git reset --hard origin/feature_branch

to make their local copy of a feature branch match what some has pushed with --force (after a rebase).

I was wondering if you would consider including this scenario at http://marklodato.github.com/visual-git-guide/index-en.html#reset

@MarkLodato
Copy link
Owner

I do explain --hard but fail to give any examples of why one would want to use it. I think this can be made into a more general request to give such examples for most cases. For example, I should also explain when git reset -p / git reset -- files should be used.

@ghost ghost assigned MarkLodato Mar 17, 2013
@pdurbin
Copy link
Author

pdurbin commented Mar 17, 2013

Right, you do say "if --hard is given, the working directory is also updated" but I love real world examples. I'm still not sure how common...

git reset --hard origin/feature_branch

... is but @ironcamel calls it a "pretty standard workflow" (in combination with git rebase) so maybe it would be a decent use case for your guide. Thanks for considering it! :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants