/
/
/
# What does this implement/fix? #5499 added a `push`-on-`dev` trigger that re-cuts dependency bump PRs stranded by a merge conflict. It never fires: auto-merge is enabled with `GITHUB_TOKEN`, so the merge actor is `github-actions`, and GitHub suppresses workflow triggers for events caused by `GITHUB_TOKEN`. The workflow has zero `push`-event runs, and #5528 sat in conflict after #5527 merged. - Enable auto-merge with a `musicassistant-bot` App token (same minting + identity check as `refresh-stale`), so the merge push triggers the refresh. Approval stays on `GITHUB_TOKEN` since the App cannot approve its own PR. - Add a `workflow_dispatch` trigger as a manual drain for already-stranded PRs, and accept it in the `discover-stale` gate. Note: bump merges to `dev` now also trigger the other `push` workflows (test, release drafter), which `GITHUB_TOKEN` merges silently suppressed. **Related issue (if applicable):** - related issue <link to issue> ## Types of changes <!-- Tick exactly one box. CI (.github/workflows/pr-labels.yaml) derives the label from the ticked box and applies it automatically; the release-notes generator uses that same label to slot this change into the next release notes. --> - [ ] Bugfix (non-breaking change which fixes an issue) — `bugfix` - [ ] New feature (non-breaking change which adds functionality) — `new-feature` - [ ] Enhancement to an existing feature — `enhancement` - [ ] New music/player/metadata/plugin provider — `new-provider` - [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected) — `breaking-change` - [ ] Refactor (no behaviour change) — `refactor` - [ ] Documentation only — `documentation` - [ ] Maintenance / chore — `maintenance` - [x] CI / workflow change — `ci` - [ ] Dependencies bump — `dependencies` ## Checklist - [x] The code change is tested and works locally. - [x] `pre-commit run --all-files` passes. - [ ] `pytest` passes, and tests have been added/updated under `tests/` where applicable. - [ ] For changes to shared models, the companion PR in `music-assistant/models` is linked. - [ ] For changes affecting the UI, the companion PR in `music-assistant/frontend` is linked. - [x] I have read and complied with the project's [AI Policy](https://github.com/music-assistant/.github/blob/main/AI_POLICY.md) for any AI-assisted contributions. - [ ] I have [raised a PR against the documentation repository](https://github.com/music-assistant/music-assistant.io/blob/main/CONTRIBUTING.md) targeting the main or beta branch as appropriate.