We released DevSensei | Code Owners for Bitbucket 8.9 on 🎉
Download on the Atlassian Marketplace for Data Center
Features
🆕 Report results of Add Reviewers action
add-comment action can now report the results of other actions previously occurring in the same workflow.
Why? Continuing our work to split up the add-codeowners action into fine-grained features, we have reintroduced the commenting functionality via the add-comment action.
Can you show me an example?
below you can see the new report-from option that accepts a key associated with a previous action in the workflow. For now only add-reviewers is a valid key, but we hope to expand the options in the future.
# This would be added within a workflow
actions:
- add-reviewers:
members: codeowners
assignment-routing:
random: 1
- add-comment:
report-from: add-reviewers
task: false
This will result in the same comment behavior that you may already use with CODEOWNERS file or the previous add-codeowners action:
Change to automatic CODEOWNERS migration
The automatic process to migrate a CODEOWNERS file, accessible from the in-app DevSensei Documentation, now produces a workflow with a mixture of add-reviewers, add-comment and unapprove actions in the actions section, codeowners and custom-groups in the custom-attributes section, and codeowners-check in the merge-checks section.
This change makes each individual configuration more regular with the rest of DevSensei, unlike the irregular add-codeowners action which combined many separate features.
Changelog
🐛 Bugfixes 8.9.0
-
No bug fixes since the previous release
Previous: Release Notes v8.7
Do you have any questions, suggestions, or problems?
Let us know. We’re glad to help!