We'd love to accept your code patches!
If you need to define, parse, and read command line flags, please use Abseil's Flag library for Command Line Parsing, which is easy to use and out of box.
They are useful, please use them. GitHub Actions CI runs on every pull request, so it will tell you if your commit will break the code. Also, common sense, add tests whenever you commit large chunk of code.
Before you merge you local branch to master branch, please use git rebase when merging changes from the master branch and use git rebase -i HEAD~<n> to clean up or squash your local commit histories, so you don't have any funky duplicate commit messages, or unwanted commits.
Please, if possible, follow the commit message style guide:
[commit type] commit messages
body (changes, links, attributions, etc)
issue tracker id (for reference)
where commit type is one of feat, fix, docs, style, refactor, chore, test etc.
Please, if possible, follow Google C++ style guide. If you use an IDE or any common text editors, they have extensions that help you auto format and lint your code for style errors.