Only surfaces checks that are specific to the code modified in the Pull Request.
Checklists can act as a reminder or a hard blocker for merging Pull Requests.
Pull Checklist is technology and stack agnostic. Works with anything that utilizes Github.
Pull Checklist goes beyond "Pass or Fail"
If a developer modifies a business-sensitive class, a class-specific checklist can remind them of common pitfalls or best practices for that area.
After a Pull Request is created, a contextually relevant checklist is added as a PR comment.
Checklists are tailored to suit your workflow with specific conditions that can are easily managed.
"This is a no-brainer. I think you're going to love it 🏆"
|/ month||/ month||/ month|
|Checklist TypesAdd different checklists for respective use-cases or areas of your codebase.||1||4||Unlimited|
|Checklist ConditionsCustomize which conditions or areas of your codebase should trigger a Checklist.||Unlimited||Unlimited||Unlimited|
|Protected Pull RequestsIf a Pull Request matches the conditions of a checklist type, that checklist is added to your PR comments in Github.||10||50||500|
|Login with GitHub||Login with GitHub||Login with GitHub|
...which config value do we update for each deployment?
...why was that Class implemented so strangely last year?
It is hard to remember these answers all the time.
You don't need to anymore.
Pull Checklist helps hundreds of dev teams safely modify code that requires extra context and safety checks.
This is a tool for developers ~ by developers.