Pre-flight installs statistics

Automatically build task lists for every pull request based on information in your commit messages.

Pre-flight automatically and continuously collects the tasks you've mentioned in your commit messages and adds them as a task list to the pull request's description. It will also display a failed check on the pull request until all tasks are marked as completed.

Usage

Whenever you're committing a change, if that change will require some manual action to happen before it's merged to production (or to any other environment, for that matter), you put down tasks inside the commit message. A basic task looks like this -

[]: don't forget that important thing

Just a pair for square brackets, followed by a colon and then the task definition. The task definition can be as long as you like, but can't contain line breaks. There will also be an easy link to the commit, so you can add more details in the rest of the commit message.

Branch Conditioning

By default, any PR will collect all the tasks in all of it's commits. However, sometimes a task is only relevant for a specific environment. For example, you may want to only show the task when merging to master. In that case, the syntax is -

[](master): I'm only relevant for production

You can also specify multiple branches using pipes -

[](master|dev): I'm only relevant for prod/staging

Description from the GitHub Marketplace listing.