Releases: OSS-Docs-Tools/code-owner-self-merge
Releases · OSS-Docs-Tools/code-owner-self-merge
1.6.6
What's Changed
- Actions URI has changed. Update to use correct URI. by @stoovon in #37
- Update version string by @hyperupcall in #41
- Add
ownerNoPings
option to prevent GitHub pings by @hyperupcall in #43 - ci: Update actions and set minimal Node.js version to v14 by @hyperupcall in #44
- Do not early return when no relevant code owner exists by @saschanaz in #40
New Contributors
- @stoovon made their first contribution in #37
- @hyperupcall made their first contribution in #41
Full Changelog: 1.6.5...1.6.6
1.6.5
Adds a quiet
option which skips saying who can merge a PR
Full Changelog: 1.6.4...1.6.5
Attributes correctly
Merging now sets the right author
1.6.2
Minor bug fix for closing issues
Merge pull request #31 from saschanaz/patch-1 Use `issues.update` for closing both issues and PRs
Codeowners can close PR/Issues
With 1.6.0 - thanks to @saschanaz any named Codeowner has the ability to close any PR or Issue.
Given that closing is at most a nuisance, and not a potential security issue we opted for a lower level of access requirements (plus the owner to files mapping doesn't make sense for issues)
Minor bug fix
1.5.4 Fix API for adding custom label
Explicit fallback to maintainers
We can use this action to make it explicit when something isn't covered by folks in the CODEOWNER:
- name: Run Codeowners merge check
uses: OSS-Docs-Tools/code-owner-self-merge@v1
env:
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
with:
merge_method: 'squash'
if_no_maintainers_add_label: 'maintainers'
if_no_maintainers_assign: '@orta @sandersn'
Merge Strats and Redundant Statuses
Featuring work from @diogotcorreia
Minor bugfix
1.5.1 Handle casing correctly with the PR status