adding draft-branch to power ghpages #31
Merged
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
|
Trying out : manubot/rootstock#341 |
cgreene
approved these changes
May 22, 2020
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.
Purpose
Our intention is to have gh-pages rendered from both draft-branch as well as master. Since most PRs will be against draft-branch, it would be great to have ease of readability for both branches.
The draft-branch (dev branch) will be reviewed more regularly as and when PRs are merged.
The master branch (prod-ready) will be reviewed more intermittently when substantial sections have been finished.
Directions for reviewers
this is a test
Which areas should receive a particularly close look?
none
Is there anything that you want to discuss further?
none
Is the pull request ready for review?
Manuscript checklist
NA