|author||Gregory Meinke <email@example.com>||Tue Dec 18 17:33:55 2018|
|committer||chrome-bot <firstname.lastname@example.org>||Tue Dec 18 20:16:35 2018|
doc: remove cros_config testing doc from docs dir This document has been moved to the corresponding tast test directory. BUG=none TEST=none Change-Id: Ia017701646bd71f5c4b1d20214ba1142fe3872c3 Reviewed-on: https://chromium-review.googlesource.com/1382613 Commit-Ready: Gregory Meinke <email@example.com> Tested-by: Gregory Meinke <firstname.lastname@example.org> Reviewed-by: Dan Erat <email@example.com> Reviewed-by: Mike Frysinger <firstname.lastname@example.org>
Markdown documents must follow the style guide.
This repository is managed by the repo tool, so you can make changes to it using the same techniques that you'd use for any other repositories in the project.
See the Contributing guide for more details.
You can also make changes to this repository without using the repo tool. This comes in handy when you don't have a Chromium OS checkout:
git clone https://chromium.googlesource.com/chromiumos/docs curl -Lo .git/hooks/commit-msg https://gerrit-review.googlesource.com/tools/hooks/commit-msg chmod +x .git/hooks/commit-msg cd docs git checkout -b changes (make some changes) git commit -a git push origin HEAD:refs/for/master
The above steps will upload a patch to chromium-review.googlesource.com where you can get your patch reviewed, and submit.
You can preview your local changes using
You can also use md_browser, which is entirely local and does not require refs/sandbox/ push permission, but has somewhat inaccurate rendering:
# at top of Chromium OS checkout ./chromium/src/tools/md_browser/md_browser.py -d docs
Then browse to e.g. http://localhost:8080/README.md.
To review someone else's changes, apply them locally first, or just click the
gitiles link near the top of a Gerrit file diff page.