Enable automatic elastic.co doc builds for internal users #3940
Conversation
This file contains 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 pull request does not have a backport label. Could you fix it @bmorelli25? 🙏
|
mergify
bot
added
the
backport-skip
colleenmcginnis
approved these changes
May 29, 2024
None here. I echo your concerns raised elsewhere about implementing this in other repos we can't control, but this PR is fine. |
scottybollinger
approved these changes
May 29, 2024
|
@bmorelli25 can you add a description to this PR so we're not confused what it is later? |
|
Done! Thank you both! |
bmorelli25
added a commit
to bmorelli25/observability-docs
that referenced
this pull request
May 29, 2024
…astic#3940)" This reverts commit 09f1e52.
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.
Summary
This PR removes the
ci:doc-buildlabel requirement for elastic.co doc builds. PRs opened by Elastic contributors will run this action automatically now. PRs opened by community members will need to have the action manually run.To approve and run an action: Go to the Conversation tab, and under "Workflow(s) awaiting approval", click Approve and run.