Skip to content

Conversation

@swiatekm
Copy link
Contributor

What does this PR do?

Why is it important?

Checklist

  • I have read and understood the pull request guidelines of this project.
  • My code follows the style guidelines of this project
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • I have made corresponding change to the default configuration files
  • I have added tests that prove my fix is effective or that my feature works
  • I have added an entry in ./changelog/fragments using the changelog tool
  • I have added an integration test or an E2E test

Disruptive User Impact

How to test this PR locally

Related issues

Questions to ask yourself

  • How are we going to support this in production?
  • How are we going to measure its adoption?
  • How are we going to debug this?
  • What are the metrics I should take care of?
  • ...

@mergify
Copy link
Contributor

mergify bot commented Dec 15, 2025

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

  • backport-./d./d is the label that automatically backports to the 8./d branch. /d is the digit
  • backport-active-all is the label that automatically backports to all active branches.
  • backport-active-8 is the label that automatically backports to all active minor branches for the 8 major.
  • backport-active-9 is the label that automatically backports to all active minor branches for the 9 major.

@swiatekm swiatekm force-pushed the ci/buildkite-to-mage branch from 483387e to 7588e3e Compare December 16, 2025 11:20
@mergify
Copy link
Contributor

mergify bot commented Dec 16, 2025

This pull request is now in conflicts. Could you fix it? 🙏
To fixup this pull request, you can check out it locally. See documentation: https://help.github.com/articles/checking-out-pull-requests-locally/

git fetch upstream
git checkout -b ci/buildkite-to-mage upstream/ci/buildkite-to-mage
git merge upstream/main
git push upstream ci/buildkite-to-mage

@swiatekm swiatekm force-pushed the ci/buildkite-to-mage branch from 7588e3e to 5e618a6 Compare December 16, 2025 11:22
@swiatekm swiatekm changed the title Ci/buildkite to mage Generate buildkite pipelines from Go code Dec 16, 2025
@elasticmachine
Copy link
Contributor

💔 Build Failed

Failed CI Steps

History

cc @swiatekm

@mergify
Copy link
Contributor

mergify bot commented Dec 16, 2025

This pull request is now in conflicts. Could you fix it? 🙏
To fixup this pull request, you can check out it locally. See documentation: https://help.github.com/articles/checking-out-pull-requests-locally/

git fetch upstream
git checkout -b ci/buildkite-to-mage upstream/ci/buildkite-to-mage
git merge upstream/main
git push upstream ci/buildkite-to-mage

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants