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.

Sign up for GitHub

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

Jump to bottom

[8.x](backport #41119) Add a known issue entry for 8.15.0 and 8.15.2 referencing https://github.com/elastic/beats/issues/41118 #41125

Open
wants to merge 3 commits into
base: 8.x
Choose a base branch
from
Open

[8.x](backport #41119) Add a known issue entry for 8.15.0 and 8.15.2 referencing https://github.com/elastic/beats/issues/41118 #41125

wants to merge 3 commits into from

Conversation

mergify[bot]
Copy link
Contributor

@mergify mergify bot commented Oct 4, 2024

Proposed commit message

See title

Checklist

  • [ ] 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.next.asciidoc or CHANGELOG-developer.next.asciidoc.

## Disruptive User Impact
## Author's Checklist
## How to test this PR locally

Related issues

## Use cases
## Screenshots
## Logs

This is an automatic backport of pull request #41119 done by [Mergify](https://mergify.com).

@belimawr @mergify
Add container logging known issue (#41119)
dcab0ba 
Add a known issue entry for 8.15.0 and 8.15.2 referencing
#41118.

(cherry picked from commit 9d87afa)

# Conflicts:
#	CHANGELOG.asciidoc
@mergify mergify bot added backport conflicts There is a conflict in the backported pull request labels Oct 4, 2024
@mergify Mergify
Copy link
Contributor Author

mergify bot commented Oct 4, 2024

Cherry-pick of 9d87afa has failed:

On branch mergify/bp/8.x/pr-41119
Your branch is up to date with 'origin/8.x'.

You are currently cherry-picking commit 9d87afaaf3.
  (fix conflicts and run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

Unmerged paths:
  (use "git add <file>..." to mark resolution)
	both modified:   CHANGELOG.asciidoc

no changes added to commit (use "git add" and/or "git commit -a")

To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally

@botelastic botelastic bot added the needs_team Indicates that the issue/PR needs a Team:* label label Oct 4, 2024
@botelastic
Copy link

botelastic bot commented Oct 4, 2024

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

@mergify Mergify
Copy link
Contributor Author

mergify bot commented Oct 7, 2024

This pull request has not been merged yet. Could you please review and merge it @belimawr? 🙏

1 similar comment
@mergify Mergify
Copy link
Contributor Author

mergify bot commented Oct 14, 2024

This pull request has not been merged yet. Could you please review and merge it @belimawr? 🙏

@mergify Mergify
Copy link
Contributor Author

mergify bot commented Oct 21, 2024

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 mergify/bp/8.x/pr-41119 upstream/mergify/bp/8.x/pr-41119
git merge upstream/8.x
git push upstream mergify/bp/8.x/pr-41119

@mergify Mergify
Copy link
Contributor Author

mergify bot commented Oct 21, 2024

This pull request has not been merged yet. Could you please review and merge it @belimawr? 🙏

8 similar comments
@mergify Mergify
Copy link
Contributor Author

mergify bot commented Oct 28, 2024

This pull request has not been merged yet. Could you please review and merge it @belimawr? 🙏

@mergify Mergify
Copy link
Contributor Author

mergify bot commented Nov 4, 2024

This pull request has not been merged yet. Could you please review and merge it @belimawr? 🙏

@mergify Mergify
Copy link
Contributor Author

mergify bot commented Nov 11, 2024

This pull request has not been merged yet. Could you please review and merge it @belimawr? 🙏

@mergify Mergify
Copy link
Contributor Author

mergify bot commented Nov 18, 2024

This pull request has not been merged yet. Could you please review and merge it @belimawr? 🙏

@mergify Mergify
Copy link
Contributor Author

mergify bot commented Nov 25, 2024

This pull request has not been merged yet. Could you please review and merge it @belimawr? 🙏

@mergify Mergify
Copy link
Contributor Author

mergify bot commented Dec 2, 2024

This pull request has not been merged yet. Could you please review and merge it @belimawr? 🙏

@mergify Mergify
Copy link
Contributor Author

mergify bot commented Dec 9, 2024

This pull request has not been merged yet. Could you please review and merge it @belimawr? 🙏

@mergify Mergify
Copy link
Contributor Author

mergify bot commented Dec 16, 2024

This pull request has not been merged yet. Could you please review and merge it @belimawr? 🙏

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

@belimawr belimawr

Labels
backport conflicts There is a conflict in the backported pull request needs_team Indicates that the issue/PR needs a Team:* label
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
1 participant
@belimawr