- Automated bugzilla, github, and trello references
- Auto-merging approved & passing PRs
- Canceling stale Travis-CI builds
For example let's say you fixed Issue 16582 and make a PR for on GitHub. If one of your commits mentions the issue, e.g. like this Git commit message:
fix Issue 16582 - ParameterDefaults fails w/ scope parameter
The Dlang-Bot will do all the hard work of linking and referencing between Bugzilla, GitHub and Trello do for you.
It would comment on GitHub with list of all mentioned issues and link them to Bugzilla:
The first column of the table is the current status of the referenced issue.
For the Trello board it will also provide a reference:
And once a PR gets merged, the bot moves the linked Trello card to "Testing / Review".
Once a PR has been merged (i.e. the commits got pushed to master or stable), GitHub's Bugzilla integration will automatically comment to Bugzilla with a regarding commit:
Of course it will also automatically close the references issues (at least if either "fix", "close" or "address" occurs before the issue id).
Using this syntax is also very important because for the changelog generation, the git history will be used. Thus only if the Dlang-Bot has detected an issue and commented on your PR it can become part of the changelog.
- one can mention multiple issues in one commit and/or multiple commits
- the exact RegEx is:
((close|fix|address)e?(s|d)? )?(ticket|bug|tracker item|issue)s?:? *([\d ,\+&#and]+)
(the GitHub Bugzilla integration and the Dlang-Bot use the same RegEx to parse git commit messages)
At the moment the Dlang-Bot supports merging via special auto-merge and
auto-merge-squash labels. The later will perform a squashed merge of all commits
in the PR into a single one.
A reviewer can toggle a PR for "auto-merge" by simply adding the auto-merge label
(auto-merge-squash respectively).
- this relies on the "restricted branches" feature of GitHub (the Dlang-Bot will send the attempt to merge to the GitHub API)
- once a new commit event occurs (push, synchronization) the Dlang-Bot will automatically remove set all auto-merge labels from the PR
- for status events the GitHub API doesn't allow to get an information about the
- the Dlang-Bot will then try to restart the PR on every new event.
- concerning PR of the commit (thus all potential auto-merge PRs are checked)
Note: at the moment the Dlang-Bot doesn't store any authentication token, so it can't perform actions on behalf of others.
To avoid wasteful resource consumption with Travis CI, the Dlang-Bot will automatically cancel the previous, possibly running build of a PR on a new commit event (push or synchronization by a user).
