Conversation
…ust permissions Co-authored-by: Copilot <copilot@github.com>
There was a problem hiding this comment.
Pull request overview
Updates the GitHub Actions release automation by separating PR autolabeling into its own workflow and tightening permissions for the release-drafter workflow.
Changes:
- Remove
pull_requesttrigger from the main release-drafter workflow and reduce its PR permission scope. - Add a dedicated
release-drafterautolabeler workflow that runs on PR events (including fork-safe handling viapull_request_target). - Adjust release-drafter inputs (e.g.,
commitish) and reformat some long YAML values.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 5 comments.
| File | Description |
|---|---|
| .github/workflows/release-drafter.yml | Restricts triggers/permissions and tweaks release-drafter + version bump PR creation configuration. |
| .github/workflows/release-drafter-autolabeler.yml | Introduces a new workflow to automatically label PRs using Release Drafter’s autolabeler. |
| commit-message: "chore: bump version to ${{ | ||
| needs.update_release_draft.outputs.resolved_version }}" |
There was a problem hiding this comment.
commit-message is split across multiple YAML lines inside a double-quoted string. YAML will include a newline here, so the actual commit subject becomes chore: bump version to ${{ and the resolved_version ends up on the next line, producing an unintended (and likely invalid) commit message. Keep the expression on a single line or use a folded scalar (>-) so the resulting string has no newline.
| commit-message: "chore: bump version to ${{ | |
| needs.update_release_draft.outputs.resolved_version }}" | |
| commit-message: "chore: bump version to ${{ needs.update_release_draft.outputs.resolved_version }}" |
| pull_request: | ||
| types: [ opened, reopened, synchronize ] | ||
| pull_request_target: | ||
| types: [ opened, reopened, synchronize ] | ||
|
|
There was a problem hiding this comment.
This workflow listens to both pull_request and pull_request_target. For same-repo PRs, both events will fire, so you’ll get an extra (skipped) workflow run due to the if: guard. To reduce runner usage/noise, consider using a single event (typically pull_request_target) and handling fork vs same-repo behavior solely in the if: condition.
AniTrend Pull Request
Thank you for contributing! Please take a moment to review our contributing guidelines to make the process easy and effective for everyone involved.
Please open an issue before embarking on any significant pull request, especially those that add a new library or change existing tests, otherwise you risk spending a lot of time working on something that might not end up being merged into the project.
Before opening a pull request, please ensure you've done the following:
mainand targetsmain(where applicable)Types of changes
IMPORTANT: By submitting a patch, you agree to allow the project owners to license your work under the terms of the Apache License, Version 2.0.