Before Merge to Master Checklist
Before Merge to Master Checklist
At where I work, we have a production go-live checklist. It’s great for the initial launch of a project. It made me wonder if open source…
At where I work, we have a production go-live checklist. It’s great for the initial launch of a project. It made me wonder if open source projects have similar things.
I think many open-source projects have such checklists. But I haven’t seen many barebones checklists for others to build off of.
Feel free to steal this list. Literally rip it off. I don’t care about attribution as long as you do these things and enforce them.
Is your branch caught up to master?
Are there tests to cover the code you’ve added or changed?
Is the build passing?
Are you following the project’s style guide?
Have you updated the appropriate code comments, changelog, or readme?
Does the pull request have a descriptive headline and summary?
Have you given time for at least 1 person to review the changes?
Depending on the project, I suspect that in-browser tests or even real deployments with docker might be necessary.
What are your thoughts? Is there anything big I missed?