feat(bitbucket-server): extend CODEOWNER support#37161
feat(bitbucket-server): extend CODEOWNER support#37161rarkins merged 31 commits intorenovatebot:mainfrom
CODEOWNER support#37161Conversation
|
Thanks for the PR! Do you think that some parts can be separated into smaller PRs so it's easier to review? For eg. the |
Thanks for your early feedback. The refactor in addReviewers is strictly related to the CODEOWNERS implementation. However, it can be regarded as a seperate change. I will split the PR! |
708deec to
0ddc4a6
Compare
* Implements extractRulesFromCodeOwnersLines for BitBucket Server Signed-off-by: portly-halicore-76 <170707699+portly-halicore-76@users.noreply.github.com>
0ddc4a6 to
9a75f13
Compare
Signed-off-by: portly-halicore-76 <170707699+portly-halicore-76@users.noreply.github.com>
CODEOWNER support
|
@viceice why is this marked as draft? Because of the testCoverage not met? |
because it depends on |
Co-authored-by: Anne Stellingwerf <1637358+astellingwerf@users.noreply.github.com>
Signed-off-by: portly-halicore-76 <170707699+portly-halicore-76@users.noreply.github.com>
Signed-off-by: portly-halicore-76 <170707699+portly-halicore-76@users.noreply.github.com>
Signed-off-by: portly-halicore-76 <170707699+portly-halicore-76@users.noreply.github.com>
Signed-off-by: portly-halicore-76 <170707699+portly-halicore-76@users.noreply.github.com>
Signed-off-by: portly-halicore-76 <170707699+portly-halicore-76@users.noreply.github.com>
Co-authored-by: Michael Kriese <michael.kriese@gmx.de>
Co-authored-by: Michael Kriese <michael.kriese@gmx.de>
Head branch was pushed to by a user without write access
…wners-and-expandusergroups
Signed-off-by: portly-halicore-76 <170707699+portly-halicore-76@users.noreply.github.com>
Signed-off-by: portly-halicore-76 <170707699+portly-halicore-76@users.noreply.github.com>
Signed-off-by: portly-halicore-76 <170707699+portly-halicore-76@users.noreply.github.com>
|
🎉 This PR is included in version 41.72.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Changes
As described in the discussion here: #36996 I've implemented the BitBucket Server CODEOWNER logic. This includes:
Context
See related Discussion. More info about CODEOWNERS for BitBucket server can be found here
Documentation (please check one with an [x])
I believe I can't update that the expandUserGroups configuration option is implemented for BitBucket server as well, Is that generated documentation?
How I've tested my work (please select one)
I have verified these changes via: