Listed 13 November 2014 · London · United Kingdom
GitCop.
A webhook bot that checked every commit in a GitHub pull request against a repository's message rules and left a comment when one broke them.
Developer tools
Timeline
- On record
GitCop was introduced on Hacker News as automated commit message validation for GitHub pull requests, free for open source projects.
On record · Announced - Listed on Stompstart
“Automated Commit Message Validation for GitHub Pull Requests”
- Listing page saved
The Wayback Machine saved this listing page.
As listed on Stompstart
“Automated Commit Message Validation for GitHub Pull Requests”
GitCop works via webhooks on your GitHub repository. Any time a pull request is raised on your repository, each commit in the pull request is checked against the repository rules. Of any commits do not follow the provided rules, a comment is left against the pull request. GitCop features several rules that you can apply to your repository. These include specifying the length and format of the commit message. You can also customize the header and footer that are displayed next the GitHub comment. If you don't want the GitCop bot to be the one leaving messages on your repositories, you can link your own using an existing GitHub account for your company. This bot will be used on any comments for that repository.
- Location
- London · United Kingdom
In our words: The 2014 listing described GitCop as webhook-based validation for GitHub pull requests, with rules for commit message length and format, customisable comment headers and footers, and the option to post comments from a company's own GitHub bot account.
See the saved page ↗Publication record
- Release
sha256:ac5dd8d905c00eace5353304a9456358eede4224f3a935465432ab184b4d049a- Revision
sha256:fec5a86252d8f067a0a4d902b47f028a96e639c395c18c92a359527f82b821d5
Every statement here carries its date and stays true as of that date.