The only thing that I'd add is that you should clean up your git commits in your feature branch before creating a PR. This is easily done with git commit --amend and squashing. Adding the -m option allows you to pass in a new message from the command line without being prompted to open an editor. git commit --amend -m "an updated commit message" # Edit hello. py and main. py git add hello. py git commit # Realize you forgot to add the changes from main. py git add main. py git commit --amend -- no - edit https://deepsource.io/blog/git-best-practices/ feat: add beta sequence ^--^ ^---------------^ | | | +-> Summary in present tense. | +-------> Type: chore, docs, feat, fix, refactor, style, or test.