[docs] document yarn.lock backport rules#132883
Merged
watson merged 3 commits intoelastic:mainfrom May 25, 2022
Merged
Conversation
Contributor
|
Pinging @elastic/kibana-security (Team:Security) |
Contributor
|
Pinging @elastic/kibana-docs (Team:Docs) |
stacey-gammon
approved these changes
May 25, 2022
jportner
approved these changes
May 25, 2022
Contributor
jportner
left a comment
There was a problem hiding this comment.
I agree with Stacey's suggestion -- aside from that, LGTM!
Co-authored-by: Stacey Gammon <gammon@elastic.co>
|
The dev docs system only uses main for right now, but they do eventually hope to render per-version, so I would backport just to be prepared for when they do! |
💚 Build SucceededMetrics [docs]
History
To update your PR or re-run it, just comment with: cc @watson |
kibanamachine
pushed a commit
that referenced
this pull request
May 25, 2022
(cherry picked from commit 2ade119)
kibanamachine
pushed a commit
that referenced
this pull request
May 25, 2022
(cherry picked from commit 2ade119)
kibanamachine
pushed a commit
that referenced
this pull request
May 25, 2022
(cherry picked from commit 2ade119)
kibanamachine
pushed a commit
that referenced
this pull request
May 25, 2022
(cherry picked from commit 2ade119)
kibanamachine
pushed a commit
that referenced
this pull request
May 25, 2022
(cherry picked from commit 2ade119)
Contributor
💚 All backports created successfully
Note: Successful backport PRs will be merged automatically after passing CI. Questions ?Please refer to the Backport tool documentation |
kibanamachine
added a commit
that referenced
this pull request
May 25, 2022
kibanamachine
added a commit
that referenced
this pull request
May 25, 2022
Contributor
|
Looks like this PR has backport PRs but they still haven't been merged. Please merge them ASAP to keep the branches relatively in sync. |
watson
pushed a commit
that referenced
this pull request
May 30, 2022
kibanamachine
added a commit
that referenced
this pull request
May 30, 2022
kibanamachine
added a commit
that referenced
this pull request
May 30, 2022
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
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.
Related PR: https://github.com/elastic/dev/pull/2025
Todo
dev_docs/contributing/how_we_use_github.mdxpage exists as far back as7.16as far as I can see. With normal doc changes we do want to backport, but I'm not sure if this applies for docs published underdocs.elastic.devas well? ping @elastic/docs