Skip to content

ci: fix ci.yml branch triggers on 8.1 branch - #1292

Merged
mmattel merged 1 commit into
8.1from
ci/self-referential-triggers-8.1
Jul 15, 2026
Merged

ci: fix ci.yml branch triggers on 8.1 branch#1292
mmattel merged 1 commit into
8.1from
ci/self-referential-triggers-8.1

Conversation

@DeepDiver1975

Copy link
Copy Markdown
Member

What

Fix the push/pull_request branch filters in .github/workflows/ci.yml on the 8.1 branch so CI actually runs for this release line.

Why (this is a real bug, not just cleanup)

8.1's ci.yml was copied from master without adjusting its triggers:

  • pull_request.branches was masterPRs targeting 8.1 never ran the docs build
  • push.branches was master, 8.0, 7.3 (no 8.1) → pushes to 8.1 never ran either

GitHub Actions matches the branches: filter against the ref the event fires on, using the ci.yml that lives on that ref — so the filter on the 8.1 branch must name 8.1.

Part of a coordinated cleanup making each branch's ci.yml self-referential (companion PRs: #1291 for master, plus 8.0 and 7.3).

Change

  • push.branches: master, 8.0, 7.3'8.1'
  • pull_request.branches: master'8.1'

No jobs: changes.

Verification

After this PR opens, the Build documentation check should appear and run against it — before this fix it does not run at all.

🤖 Generated with Claude Code

The 8.1 ci.yml was copied from master without adjusting its triggers:
pull_request.branches pointed at master and push.branches omitted 8.1,
so PRs against 8.1 and pushes to 8.1 never built the docs. GitHub
matches branches: against the ref the event fires on, so the filter
must name 8.1. Make both push and pull_request self-referential to 8.1.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Signed-off-by: Thomas Müller <1005065+DeepDiver1975@users.noreply.github.com>
@mmattel
mmattel merged commit 46c9efe into 8.1 Jul 15, 2026
2 checks passed
@mmattel
mmattel deleted the ci/self-referential-triggers-8.1 branch July 15, 2026 08:32
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.

2 participants