Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

62 document publish #63

Open
wants to merge 3 commits into
base: master
from

Conversation

Projects
None yet
2 participants
@andrew-codes
Copy link
Collaborator

commented May 8, 2019

Closes #62

@andrew-codes andrew-codes changed the base branch from next to master May 8, 2019

kmmarsh and others added some commits Apr 29, 2019

@andrew-codes andrew-codes changed the base branch from master to next May 9, 2019

@andrew-codes andrew-codes force-pushed the 62-Document-Publish branch from b90849b to d1f98dc May 9, 2019

@andrew-codes andrew-codes changed the base branch from next to master May 9, 2019

@andrew-codes andrew-codes requested review from kmmarsh, aleytze and walkerrandolphsmith and removed request for walkerrandolphsmith May 9, 2019

@andrew-codes andrew-codes marked this pull request as ready for review May 9, 2019


### Publishing Major Versions

`next` should be merged into `master` before publishing a major version, as it will become the new `master` branch after publishing.

This comment has been minimized.

Copy link
@kmmarsh

kmmarsh May 10, 2019

Contributor

I think this could use an explicit statement about what the commands below do. Like the one above ("reate a production build and publish with the following:")

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.