Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[changelogs] : add processors "decode_duration", "move_fields" #33714

Merged
merged 2 commits into from
Nov 23, 2022

Conversation

kunsonx
Copy link
Contributor

@kunsonx kunsonx commented Nov 17, 2022

From pull request 31301 missed change logs.

Please check on it. @belimawr

Thanks.

@botelastic botelastic bot added the needs_team Indicates that the issue/PR needs a Team:* label label Nov 17, 2022
@botelastic
Copy link

botelastic bot commented Nov 17, 2022

This pull request doesn't have a Team:<team> label.

@mergify
Copy link
Contributor

mergify bot commented Nov 17, 2022

This pull request does not have a backport label.
If this is a bug or security fix, could you label this PR @kunsonx? 🙏.
For such, you'll need to label your PR with:

  • The upcoming major version of the Elastic Stack
  • The upcoming minor version of the Elastic Stack (if you're not pushing a breaking change)

To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

  • backport-v8./d.0 is the label to automatically backport to the 8./d branch. /d is the digit

@elasticmachine
Copy link
Collaborator

elasticmachine commented Nov 17, 2022

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS
Pipeline View Test View Changes Artifacts preview preview

Expand to view the summary

Build stats

  • Start Time: 2022-11-22T11:55:27.909+0000

  • Duration: 8 min 59 sec

❕ Flaky test report

No test was executed to be analysed.

🤖 GitHub comments

Expand to view the GitHub comments

To re-run your PR in the CI, just comment with:

  • /test : Re-trigger the build.

  • /package : Generate the packages and run the E2E tests.

  • /beats-tester : Run the installation tests with beats-tester.

  • run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)

@mergify
Copy link
Contributor

mergify bot commented Nov 18, 2022

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 main upstream/main
git merge upstream/main
git push upstream main

@rdner rdner added the backport-v8.6.0 Automated backport with mergify label Nov 23, 2022
@rdner rdner merged commit 26f5d5c into elastic:main Nov 23, 2022
mergify bot pushed a commit that referenced this pull request Nov 23, 2022
…fields" (#33714)

Co-authored-by: hxms <[email protected]>
Co-authored-by: Tiago Queiroz <[email protected]>
(cherry picked from commit 26f5d5c)
rdner pushed a commit that referenced this pull request Nov 30, 2022
…fields" (#33714) (#33787)

Co-authored-by: hxms <[email protected]>
Co-authored-by: Tiago Queiroz <[email protected]>
(cherry picked from commit 26f5d5c)

Co-authored-by: 冰天雪地 <[email protected]>
chrisberkhout pushed a commit that referenced this pull request Jun 1, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport-v8.6.0 Automated backport with mergify needs_team Indicates that the issue/PR needs a Team:* label
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants