build: publish docs-content based on branch #10020
Merged
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
Docs content will be published differently for different branches. For example, commits in `master` will be published on the `master` branch on the docs-content repository. `5.2.x` commits will be published on the `5.2.x` branch on the docs-content repository. Tags on the docs-content repository will be explicit to indicate from what branch they come.
googlebot
added
the
cla: yes
mmalerba
added
pr: lgtm
action: merge
jelbourn
pushed a commit
to jelbourn/components
that referenced
this pull request
Feb 27, 2018
|
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Docs content will be published differently for different branches. For example, commits in
masterwill be published on themasterbranch on the docs-content repository.5.2.xcommits will be published on the5.2.xbranch on the docs-content repository.Tags on the docs-content repository will be explicit to indicate from what branch they come.