Preview Markdown Changes with Gerrit

[Andrew Grieve]

One neat bonus of using the new code-review tool is that you can include links to rendered markdown changes.

1. Use new code review via:

git config --local gerrit.host true

2. Upload your change. It will show a message like:

To https://chromium.googlesource.com/chromium/src.git

 * [new branch]                GIT_HASH -> refs/for/refs/heads/master%m=0x1f412,notify=NONE

3. Craft link like:

https://chromium.googlesource.com/chromium/src/+/GIT_HASH/docs/foo.md

[Scott Graham]

Just be aware of where you're uploading the doc. I thought I was being clever doing this too, and I ended up repeatedly spamming lots of auto-CC'd people because of Gerrit's apparent enthusiasm for sending emails every time something in its data store changes.

(Nice feature to have though!)

--
--
Chromium Developers mailing list: chromi...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-dev
---
You received this message because you are subscribed to the Google Groups "Chromium-dev" group.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-dev/CABiQX1VOJcO3m8%3DAkUwzUEnHzwTRkvZUMvYSusVR53NzugmgNQ%40mail.gmail.com.

[Mike Frysinger]

there is a md_browser tool meant for local rendering/testing:

  https://chromium.googlesource.com/chromium/src/tools/md_browser/

it doesn't match gitiles's markdown exactly, but it should be good enough for most work.  the review tool doesn't matter either.

if your repo supports sandboxes, you could always push that way.  for example, in many CrOS repos, you can do:

  $ git push --force origin HEAD:refs/sandbox/$USER/foo

then browse to:

  https://chromium.googlesource.com/<repo>/+/sandbox/$USER/foo/

this avoids spamming gerrit with lots of patchsets.

-mike

--

[Dirk Pranke]

You don't actually have to craft the URL by hand, either. If you click on the review link for a particular file in your CL, there's a link to view the file in gitiles:

-- Dirk

--

[agable]

Another way to get there:

Load the main page for the review (e.g. by following the link that git-cl-upload prints), then click on the hash of the commit you uploaded, then on the file you want to see.

[Mark Mentovai]

Another tip for enhanced stealth: I found that it actually didn’t take very much effort to set up a local Gitiles instance.

To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-dev/CAAbOSckuSdADBHCUJBF%3D3iTSdaFasxC8Zzt9sze-hX1i6ZMhTA%40mail.gmail.com.

[natiq alkarakole]

To unsubscribe from this group and stop receiving emails from it, send an email to chromium-dev...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-dev/CAAbOSckuSdADBHCUJBF%3D3iTSdaFasxC8Zzt9sze-hX1i6ZMhTA%40mail.gmail.com.