Monorail: Gitignore chopsui symlink. Bug: monorail: Change-Id: I2df91872ed0449c67e5be44cf57ccd25ed3fff9a Reviewed-on: https://chromium-review.googlesource.com/992854 Reviewed-by: Jeff Carpenter <jeffcarp@chromium.org> Commit-Queue: Tiffany Zhang <zhangtiff@chromium.org> Cr-Mirrored-From: https://chromium.googlesource.com/infra/infra Cr-Mirrored-Commit: 4b74b08a5a1d8ded81084121e88b4d9a13fe26ad
Design Doc: go/chopsui
This directory contains Polymer Web Components that are meant to be shared by Chrome Operations' application frontends.
chopsui/ has been published as the bower package: chopsui
Code changes should be done in the infra repo.
New versions of the chopsui bower package are published by pushing git tags. This should be done in the chopsui repo. See the Pushing a New Version section.
Please add demos and documentation for elements as described in the polymer docs.
Check that your demo and documentation are working and correct by running:
polymer serve
then visit localhost:XXXX/components/chopsui/demo/my-el_demo.html
New versions are published by pushing git version tags while in the chopsui repo. Bower will automatically detect a new version tag.
You need to be granted permission to push tags in the chopsui repo. If you don't have permission, please contact jojwang@, zhangtiff@, or seanmccullough@ for instructions on how to proceed.
make a clone of the chopsui repo
git clone https://chromium.googlesource.com/infra/infra/crdx/chopsui
make sure chromium's depot_tools is in your path
git tag
git tag v0.0.31 # replace 0.0.31 with an appropriate version number
git push --tags
That's it! Run
bower info chopsui
You should see the new version tag you just pushed listed under ‘Available versions’.