Skip to content

Specify to use staging branch for development#859

Merged
msecret merged 5 commits into
18f-pages-stagingfrom
specify-to-use-staging-branch
Oct 26, 2015
Merged

Specify to use staging branch for development#859
msecret merged 5 commits into
18f-pages-stagingfrom
specify-to-use-staging-branch

Conversation

@fureigh

@fureigh fureigh commented Oct 22, 2015

Copy link
Copy Markdown
Contributor

Following the lead of 18f.gsa.gov's README.

@maya

maya commented Oct 23, 2015

Copy link
Copy Markdown
Contributor

Should we specify that the staging branch is 18f-pages-staging?

@fureigh

fureigh commented Oct 23, 2015

Copy link
Copy Markdown
Contributor Author

@maya Absolutely. Good catch.

Comment thread README.md Outdated

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For our production site, we currently have two URLs: https://pages.18f.gov/designstandards/ and https://playbook.cio.gov/designstandards/. Should we state both?

18F pages (https://pages.18f.gov/designstandards/) is the faster, more reliable one, but https://playbook.cio.gov/designstandards/ is what is publically known.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Updated to the publicly known one here: 6d3eb63

msecret pushed a commit that referenced this pull request Oct 26, 2015
Specify to use staging branch for development
@msecret msecret merged commit 110bd41 into 18f-pages-staging Oct 26, 2015
@maya maya deleted the specify-to-use-staging-branch branch October 26, 2015 20:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants