commit-status-publisher
commit-status-publisher copied to clipboard
TeamCity commit status publisher
Support for Gitea. Code is based on the one for Gitlab to keep the Code Style and Approach. Also the support for Gitlab had about the same scope as for...
For feature branch builds only publish status for participating commits, commits coming from default branches will be skipped
Stash sends 429 with Retry-After header; GitHub sends 403 with x-ratelimit-reset header. Both tell us when it’s ok to retry the request.
Fixes [TW-54098](https://youtrack.jetbrains.com/issue/TW-54098)
Added score filed to gerrit config, for providing not only 'verified' key.
Had an issue where the head of the merge/pull request was at the same location as the source so the status was posted to the previous iteration.
A / in repo name would cause 404 as gitlab expects encoded repo names. Having a project in a subgroup was adding a / to repo name.
Few weeks ago my Team start to using Bitbucket with Pull Request workflow, TeamCity can build our pull request branches but commit status unfortunately was not sent back to the...
Fix bug of sending the status in case of a merge request from fork repository