Module 2. Change requests and squashing

[OleksiyRudenko]

Draft

Theory: how to create a feature branch to avoid problems at PR phase and how to fix if you face this issue nevertheless

1. Author adds some code into two individual files in 4 commits, committing into a feature branch
   (commit to file A, commit to file B, commit to file A again, commit to file B again)
2. Author regroups and squashes commits per each file
3. Author pushes changes upstream
4. Code reviewer requests changes
5. Author implements changes locally
6. Code reviewer requests a change with a suggestion
7. Author accepts suggestion on GitHub
8. Code reviewer approves PR
9. Code reviewer squash-rebases PR commits onto dev
10. Repo maintainer merges changes from dev into master and tags a release