Tips on GitHub

Things on this page are fragmentary and immature notes/thoughts of the author. Please read with your own judgement!

Tips and Traps

Have at least 2 branches master and dev. Reserve the master branch for releasing purpose and the dev banch for development. Protect the master branch on GitHub to require checks to pass before merging. If it is only one person (yourself) developing on the project, do not require pull request review before merging. Otherwise, if there are multiple people developing on the projects, require pull request review (of at least 1 person) before merging.
CI workflows should be set up to make sure that the master branch is always valid.
A development (dev, daily, next, or whatever name) release should be made when a push is made into the master branch. An official tagged release should be made on creation of a new tag. A new tag should only be created on the lastest commit of the master branch!
Adblock Plus might cause some GitHub pages (e.g., the page showing changes of a PR) fail to render correctly. If you ever encounter such an issue, turn off Adblock Plus (or similar extensions) and try again. Or you can try again in the incognito mode.

https://github.com/Meituan-Dianping

https://github.com/xingshaocheng/architect-awesome#fork-destination-box

https://ai.googleblog.com/

https://coolshell.cn/

https://brendansterne.com/

https://www.raychase.net/

https://www.kawabangga.com/

https://stackoverflow.com/questions/26372417/github-oauth2-token-how-to-restrict-access-to-read-a-single-private-repo

https://github.blog/2019-06-06-generate-new-repositories-with-repository-templates/

https://mp.weixin.qq.com/s/r9dNXpoH8F5CMoHdyv6BFQ