Mergify Update: Not working on PR's from forks where workflows have been updated in main
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 339
- Forks
- 93
- PR merge metrics
- No merged PRs in 30d
Description
When opening a PR from a fork and attempting @Mergifyio update on the PR we get the following error if any workflows have been added or updated in main since the fork was created:
update
❌ Mergify doesn't have permission to update
Details
For security reasons, Mergify can't update this pull request. Try updating locally.
GitHub response: refusing to allow a GitHub App to create or update workflow .github/workflows/<updated-workflow>.yaml without workflows permission
We've confirmed that the Mergify app has workflow permissions, this appears to be a similar issue to #5055 but we're still seeing it as of today.
Expected Behavior
The fork branch gets updated from main.
Actual Behavior
The fork branch is not updated.
Steps to Reproduce the Problem
- Create a fork from a repo
- Create a PR
- Update any workflow file on the main repo
- @Mergifyio update
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the @Mergifyio update flow with a forked PR after changing a file under .github/workflows/. Start by tracing the update operation and the GitHub response about workflow permissions. Done means the fork branch updates from main without the GitHub App permission error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, github-actions
- Domain
- ci-cd, devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100