-
Notifications
You must be signed in to change notification settings - Fork 476
Home
jseldess edited this page Jul 21, 2016
·
33 revisions
Welcome to the CockroachDB docs wiki!
This page contains suggested steps for common docs tasks. It is intended for CockroachDB writers.
When you're starting a new docs project:
- Switch to
gh-pages:git checkout gh-pages. - Create a new branch:
git checkout -b "<your branch name>". - Write.
- See the files you've modified:
git status. - Stage your changes for commit:
git add .(stage all modified files) orgit add <filename>(stage specific file). - Commit your changes:
git commit -m "<good message describing changes>". - Start the Review workflow.
Once you're ready to have work reviewed:
- Push your local branch to the server (first time):
git push -u origin <branch name>. - Go to the docs repo, create a pull request with a brief description, and assign a reviewer.
- Edit your local branch based on feedback.
- Push edits to the server:
git push. - Once you get LGTM from the reviewer, merge the PR and delete the remote branch.
- Switch to
gh-pages:git checkout gh-pages. - Update
gh-pages:git pull. - Delete the local PR branch:
git branch -d <branch name>.
Once you've merged with gh-pages, TeamCity runs the files through Jekyll and syncs the output to cockroachlabs.com/testdocs. It's a good idea to check that everything looks good there before moving on to the Publish workflow.
Once you've merged your changes with gh-pages, use TeamCity to push a new version to cockroachlabs.com/docs:
- Go to teamcity.cockroachdb.com.
- If it's your first time in TeamCity, click Configure Visible Projects in the upper right and move Internal from Hidden projects to Visible projects.
- Under Internal > Docs > Production Docs, click Run. This runs
gh-pagesthrough Jekyll and syncs the output to the\docsdirectory on dreamhost. - Go to cockroachlabs.com/docs and make sure all's well.
The cockroach wiki covers all aspects of the release notes process. Basically, Ben or another dev drafts the release notes and opens a docs PR. Once that's been merged:
- Update your local
gh-pages:git pull. - Create a new branch:
git checkout -b "release-note-updates". - In the new release notes file, add links to docs, add Doc Updates, and make sure any Docs contributes are listed under Contributors.
- Make sure
versionandbuild_timeindata/strings.ymlare up-to-date. - Stage your changes for commit:
git add .(stage all modified files) orgit add <filename>(stage specific file). - Commit your changes:
git commit -m "<good message describing changes>". - Start the Review workflow.
- Get on your PR branch:
git checkout <branch name>. - Run:
make.