Create .mergify.yml with rule enabling forwardporting of documentation changes #2504
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This change is part of elastic/docs-builder#1433. In order to make the porting of documentation changes to `main` more straightforward, we are introducing a Mergify file, which contains defaults already in use by other projects, and a docs-specific ruleset.
🤖 GitHub commentsExpand to view the GitHub comments
Just comment with:
|
This was referenced Jul 31, 2025
|
@elastic/ecs can you review this please |
cotti
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
1. What does this PR do?
This change is part of elastic/docs-builder#1433.
In order to make the porting of documentation changes to
mainmore straightforward, we are introducing a Mergify file, which contains defaults already in use by other projects, and a docs-specific ruleset.2. Which ECS fields are affected/introduced?
N/A
3. Why is this change necessary?
Documentation writers will have a smoother workflow with automated forwardporting, and code owners can then decide whether to merge the changes or not.
4. Have you added/updated documentation?
N/A, self-contained
5. Have you built ECS and committed any newly generated files?
N/A
6. Have you run the ECS validation tests locally?
N/A
7. Anything else for the reviewers?
Mergify integration needs to be installed in the repository for these changes to take effect. A request is underway.
Commit Message
Create .mergify.yml with rule enabling forwardporting of documentation changes