Always Be Closing (ABC) is a GitHub App that provides several advanced features that are not provided by GitHub. Many of the features are related to Pull Request management. Any administrator of your repository can enable or disable features on an easy-to-use configuration dashboard. All the features have zero configuration options (boolean: either on or off) and are designed to be intuitive.
Install Always Be Closing via the GitHub marketplace. Select the “Configure” button on the the GitHub marketplace page to enable the service for your personal repositories or your GitHub organization. Use the configuration dashboard to enable and disable features. Leave feedback at the ABC community site.
The features include:
- Synchronize Forks
- Do Not Disturb
- Simple Pull Request Reviews
- Notify Failing Status Checks
- Delete Reaction Comments
- Delete Emoji Comments
- Monitor Git Tags
- Automatic Update Branch
- Automatic Merge
- Automatic Squash
- Automatic Rebase
- Automatic Delete Branch
ABC requires the following GitHub permissions:
- Repository administration - read-only access
- Repository metadata - read-only access
- Organization members - read-only access
- Commit statuses - read-only access
- Issues - read and write access
- Pull Requests - read and write access
- Repository contents - read and write access
If you prefer not to grant read or write access to repository contents (the code in your git repositories), try Always Be Closing Jr. It provides all the features of ABC that do not require access to repository contents.
Here are some examples of Always Be Closing features:
Enter “approve” as a comment on a pull request and ABC will automatically generate a GitHub Review on your behalf. This simplifies the process of creating a GitHub Review. The standard workflow in GitHub for approval with a GitHub Review is (1) click on “Files changed”; (2) click on “Start a review”; (3) click on “Approve”; and finally (4) click on “Submit review”.
Post a pull request comment when a status check has failed. Failing status checks to not trigger GitHub notifications. Status check notifications are typically configured on the status check service (such as in the Jenkins job configuration or the Travis CI configuration). Enabling this feature provides a standard mechanism for status check failures regardless of which service has the failure. Posting a comment on the pull request will trigger an email notification to the pull request author who then can take another look and fix their pull request.
Delete comments from pull requests that are better expressed as GitHub reactions.
Update Branch will automatically updates pull requests. When there is a new commit to the base branch, the service will merge those commits into the compare branch.
Check this page we are continuously adding new features.