DEV Community

Discussion on: Share your GitHub Tricks and Tips

Collapse
 
sudiukil profile image
Quentin Sonrel

That's general advice but I think the "default" Git(Hub) workflow should be this:

Issue > Fork > Branch > (Work) > Rebase (if needed) > PR > (Discussion & more work if need be) > Merge

IMHO that's the easiest (for you and for the original dev) way of contributing to a project using Git(Hub).

Other random things from experience:

  • Use a shitload of aliases for Git commands, but only when you are familiar with the "real" commands
  • Start small, don't get into the branching/rebasing/cherry-picking madness before mastering the Git basis
  • That's maybe outside the scope of the question but keep track of your issues and PRs with tools like Trello or GitHub's projects