Skip to content

[backport/sync-changelog] Skip changelog link check on sync PRs - #20251

Merged
mrodm merged 1 commit into
elastic:mainfrom
mrodm:add_label_sync_workflow
Jul 21, 2026
Merged

mrodm merged 1 commit into
elastic:mainfrom
mrodm:add_label_sync_workflow

Conversation

@mrodm

@mrodm mrodm commented Jul 21, 2026

Copy link
Copy Markdown
Collaborator

Summary

Add the changelog-link-check:skip label to the PRs automatically created by the sync-backport-changelog workflow.

Context

When a backport branch is pushed and its changelog.yml is updated, the sync-backport-changelog workflow creates a PR to sync those changelog entries to main. Buildkite then runs the "Check changelog PR links" step, which validates that each changelog entry's linked PR number matches the PR being merged.

These sync PRs will always fail that check: the changelog entries reference the original backport PR number, not the sync PR number. The check is therefore both irrelevant and noisy for this class of PRs.

Change

  • dev/backports/changelog/sync.go: pass --label changelog-link-check:skip alongside the existing --label backport:sync-changelog when calling gh pr create.

Related issues

Proposed commit

[backport/sync-changelog] Skip changelog link check on sync PRs

Add the `changelog-link-check:skip` label when creating sync-changelog
PRs so Buildkite does not validate changelog PR links — those links
always point to the original backport PR, not the sync PR number.

This PR was generated with the assistance of Claude (claude-sonnet-4-6).

Add the `changelog-link-check:skip` label when creating sync-changelog
PRs so Buildkite does not validate changelog PR links — those links
always point to the original backport PR, not the sync PR number.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@mrodm mrodm self-assigned this Jul 21, 2026
@mrodm
mrodm marked this pull request as ready for review July 21, 2026 10:02
@mrodm
mrodm requested a review from a team as a code owner July 21, 2026 10:02
@infra-vault-gh-plugin-prod

Copy link
Copy Markdown

💚 Build Succeeded

cc @mrodm

@bturquet bturquet left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

LGTM

@mrodm
mrodm merged commit 53384e0 into elastic:main Jul 21, 2026
9 checks passed
@mrodm
mrodm deleted the add_label_sync_workflow branch July 21, 2026 10:07
@mrodm

mrodm commented Jul 21, 2026

Copy link
Copy Markdown
Collaborator Author

@Mergifyio backport backport-aws-6.x backport-security_detection_engine-9.4

@mergify

mergify Bot commented Jul 21, 2026 •

Copy link
Copy Markdown
Contributor

backport backport-aws-6.x backport-security_detection_engine-9.4

✅ Backports have been created

Details

mrodm added a commit that referenced this pull request Jul 21, 2026
…) (#20253)

Add the `changelog-link-check:skip` label when creating sync-changelog
PRs so Buildkite does not validate changelog PR links — those links
always point to the original backport PR, not the sync PR number.


(cherry picked from commit 53384e0)

Co-authored-by: Mario Rodriguez Molins <mario.rodriguez@elastic.co>
Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>
mrodm added a commit that referenced this pull request Jul 21, 2026
…) (#20252)

Add the `changelog-link-check:skip` label when creating sync-changelog
PRs so Buildkite does not validate changelog PR links — those links
always point to the original backport PR, not the sync PR number.


(cherry picked from commit 53384e0)

Co-authored-by: Mario Rodriguez Molins <mario.rodriguez@elastic.co>
Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>
christophercutajar pushed a commit to christophercutajar/integrations that referenced this pull request Jul 21, 2026
…tic#20251)

Add the `changelog-link-check:skip` label when creating sync-changelog
PRs so Buildkite does not validate changelog PR links — those links
always point to the original backport PR, not the sync PR number.

Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>
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