Skip to content

[BUG](ci) Vnext rebase workflow needs broader permissions#541

Open
John McCall (lowlydba) wants to merge 1 commit into
mainfrom
540-bugci-vnext-rebase-workflow-has-incorrect-workflow-permissions
Open

[BUG](ci) Vnext rebase workflow needs broader permissions#541
John McCall (lowlydba) wants to merge 1 commit into
mainfrom
540-bugci-vnext-rebase-workflow-has-incorrect-workflow-permissions

Conversation

@lowlydba
Copy link
Copy Markdown
Contributor

Description

The Rebase vnext onto main had been failing until the GitHub app permissions were updated, and is now working.

This pull request makes additional workflow-level permission changes to ensure that all code paths are accounted for, whereas before there may have been latent permission errors lurking.

Reference

N/A

Testing

The workflow has been successfully re-run post updating of the App permissions, confirming it is fixed.

This is paired with an increase in scoped permissions for the underlying GHA. Not currently broken, but there are yet-to-be-triggered paths (like vnext containing a workflow change) that could error.

Signed-off-by: John McCall <john@overturemaps.org>
@github-actions
Copy link
Copy Markdown

github-actions Bot commented Jun 4, 2026

🗺️ Schema reference docs preview is live!

🌍 Preview https://staging.overturemaps.org/schema/pr/541/schema/index.html
🕐 Updated Jun 04, 2026 17:19 UTC
📝 Commit 91246a0
🔧 env SCHEMA_PREVIEW true

Note

♻️ This preview updates automatically with each push to this PR.

Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR hardens the Rebase vnext onto main GitHub Actions workflow by expanding the GitHub App installation token’s explicitly-scoped permissions so the rebase/force-push succeeds even when vnext contains changes under .github/workflows/.

Changes:

  • Adds permission-workflows: write to the actions/create-github-app-token step so pushes that modify workflow files are permitted.
  • Improves inline documentation/comments explaining why each app-token permission is needed.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[BUG](ci) Vnext rebase workflow has incorrect workflow permissions

3 participants