Skip to content

Update README.md#604

Merged
gbanasiak merged 1 commit intoelastic:masterfrom
crispybacon:patch-1
Oct 2, 2024
Merged

Update README.md#604
gbanasiak merged 1 commit intoelastic:masterfrom
crispybacon:patch-1

Conversation

@crispybacon
Copy link
Contributor

The parse tool requires the compressed file to be passed to it.

The parse tool requires the compressed file to be passed to it.
Copy link
Member

@inqueue inqueue left a comment

Choose a reason for hiding this comment

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

@gareth-ellis
Copy link
Member

buildkite test this

@gbanasiak gbanasiak merged commit 3f72278 into elastic:master Oct 2, 2024
@NickDris
Copy link
Contributor

Adding backport label just for some manual tests

@NickDris NickDris added backport pending Awaiting backport to stable release branch backport-to-8.15 and removed backport pending Awaiting backport to stable release branch labels Aug 20, 2025
@esbenchmachine
Copy link
Collaborator

💚 All backports created successfully

Status Branch Result
8.15

Note: Successful backport PRs will be merged automatically after passing CI.

Questions ?

Please refer to the Backport tool documentation and see the Github Action logs for details

esbenchmachine added a commit that referenced this pull request Aug 20, 2025
The parse tool requires the compressed file to be passed to it.

(cherry picked from commit 3f72278)

Co-authored-by: Jesse Bacon <dread.roberts@gmail.com>
@esbenchmachine esbenchmachine added the backport pending Awaiting backport to stable release branch label Dec 19, 2025
@esbenchmachine
Copy link
Collaborator

@crispybacon
A backport is pending for this PR. Please add all required vX.Y version labels.

  • If it is intended for the current Elasticsearch release version, apply the corresponding version label.
  • If it also supports past released versions, add those labels too.
  • If it only targets a future version, wait until that version label exists and then add it.
    (Each rally-tracks version label is created during the feature freeze of a new Elasticsearch branch).

Backporting entails:

  1. Ensure the correct version labels exist in this PR.
  2. Ensure backport PRs have backport label and are passing tests.
  3. Merge backport PRs (you can approve yourself and enable auto-merge).
  4. Remove backport pending label from this PR once all backport PRs are merged.

Thank you!

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

Labels

backport pending Awaiting backport to stable release branch

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants

Comments