Skip to content

ci: add mergify backport rule for 9.4 branch#18999

Open
jmikell821 wants to merge 1 commit into
elastic:mainfrom
jmikell821:fix/mergify-9.4-backport
Open

ci: add mergify backport rule for 9.4 branch#18999
jmikell821 wants to merge 1 commit into
elastic:mainfrom
jmikell821:fix/mergify-9.4-backport

Conversation

@jmikell821
Copy link
Copy Markdown
Member

This PR just adds 9.4 to mergify so that PRs labeled backport-9.4 can auto-create a backport PR.

@github-actions
Copy link
Copy Markdown
Contributor

🤖 GitHub comments

Just comment with:

  • run docs-build : Re-trigger the docs validation. (use unformatted text in the comment!)
  • run exhaustive tests : Run the exhaustive tests Buildkite pipeline.

@mergify
Copy link
Copy Markdown
Contributor

mergify Bot commented Apr 14, 2026

This pull request does not have a backport label. Could you fix it @jmikell821? 🙏
To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

  • backport-8./d is the label to automatically backport to the 8./d branch. /d is the digit.
  • If no backport is necessary, please add the backport-skip label

@donoghuc
Copy link
Copy Markdown
Member

Ah, interesting. I think this exposes a bug. I believe we attempted to automate this with

- name: Create GitHub backport label (Mergify) (minor only)
if: ${{ inputs.bump == 'minor' }}
continue-on-error: true
run: make -C .ci backport-label BACKPORT_LABEL=$BACKPORT_LABEL
env:
GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
but it is in the wrong action. I'll chase that down separately.

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