walk through git workflow for a project that requires certain branching strategy

[ConsenSys-Academy]

The Git section, Module 6, is a bit light in terms of walking through common git flows. It'd be great to use a real-world example to show forking a project, making changes, committing those changes, then issuing a PR. Also good to address what happens when you need to rebase your commits to make descriptions pass requirements by the repo or project.

[ConsenSys-Academy]

some help from @kvutien
20210607 Git Cheat sheet for ConsenSys Bootcamp.docx

[ConsenSys-Academy]

More Git everyday tips:

https://mikkel.ca/blog/git-is-my-buddy-effective-solo-developer/

[kvutien]

I found this blog very useful, but IMHO, this mikkei stuff is rather of "intemediate" leveL The reason are that

• it's about a workflow (so it's good for a beginner) but this workflow is written as a discussion among seasoned git users, not as a tutorial for beginners
• the last section ("know your tools") is super-useful, but git rebase, git commit --amend, and git commit --fixup [hash] are not exactly the first things a beginner should learn

This makes me raise a potential threat for this training: loss of focus, or loss of structure. A beginner needs hand-holding. Ideally the reading material of this basic training should be numbered in recommended sequence of reading. Maybe I should make a distinct issue?

A typical counter-example of what not to do for beginners is the github repo of orbitdb. It's very organised and explained, but despite the "welcome" title, it's daunting. It's structured , but not for a beginner.

Hint: inside the repo field-manual there is a Tutorial and the repo web3-workshop has a sample React app. The latter has not up to date API calls and I'm trying to fix it.