Skip to content

fix(check-upstream): fix startup_failure and idempotent open-pr - #5

Open
vivus-ignis wants to merge 1 commit into
mainfrom
fix-envoy-20261106
Open

vivus-ignis wants to merge 1 commit into
mainfrom
fix-envoy-20261106

Conversation

@vivus-ignis

Copy link
Copy Markdown
Contributor

Root cause

The Check upstream workflow was failing with startup_failure since the release job was added to build-envoy-fips.yml with permissions: contents: write. GitHub validates at startup that all permissions a called reusable workflow's jobs request are a subset of what the caller grants. The build job in check-upstream.yml only granted packages: write, so every scheduled run failed immediately before any job executed.

Fix

  1. Added contents: write to the build job's permissions block — required by the release job added in the build workflow. Missing permission caused startup_failure on every scheduled run.
  2. Made open-pr idempotent: detect existing remote branch via git ls-remote, use --force-with-lease, skip gh pr create if PR already exists.

Test evidence

Build workflow run on fix branch: https://github.com/gardenlinux/container-envoy/actions/runs/42217390376
Conclusion: success (all jobs passed)

…-pr idempotent

1. Add contents:write to the build job permissions block — required by the
   release job in build-envoy-fips.yml (which declared permissions: contents: write).
   GitHub validates this at startup; the missing permission caused startup_failure
   on every scheduled run since the release/SBOM job was introduced.

2. Make open-pr idempotent: detect existing remote branch via git ls-remote,
   use --force-with-lease, skip gh pr create if PR already exists.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant