Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(24)

Side by Side Diff: third_party/polymer/v1_0/components-chromium/iron-overlay-behavior/CONTRIBUTING.md

Issue 1468623004: Update Polymer from 1.2.1 -> 1.2.3 (Closed) Base URL: https://chromium.googlesource.com/chromium/src.git@travis-yml
Patch Set: local-state.html Created 5 years ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View unified diff | Download patch
OLDNEW
1 1
2 <!-- 2 <!--
3 This file is autogenerated based on 3 This file is autogenerated based on
4 https://github.com/PolymerElements/ContributionGuide/blob/master/CONTRIBUTING.md 4 https://github.com/PolymerElements/ContributionGuide/blob/master/CONTRIBUTING.md
5 5
6 If you edit that file, it will get updated everywhere else. 6 If you edit that file, it will get updated everywhere else.
7 If you edit this file, your changes will get overridden :) 7 If you edit this file, your changes will get overridden :)
8 --> 8 -->
9 # Polymer Elements 9 # Polymer Elements
10 ## Guide for Contributors 10 ## Guide for Contributors
(...skipping 52 matching lines...) Expand 10 before | Expand all | Expand 10 after
63 63
64 2. **A succinct description of the design** used to fix any related issues. For example: 64 2. **A succinct description of the design** used to fix any related issues. For example:
65 65
66 ```markdown 66 ```markdown
67 This fixes #20 by removing styles that leaked which would cause the page to tur n pink whenever `paper-foo` is clicked. 67 This fixes #20 by removing styles that leaked which would cause the page to tur n pink whenever `paper-foo` is clicked.
68 ``` 68 ```
69 69
70 3. **At least one test for each bug fixed or feature added** as part of the pul l request. Pull requests that fix bugs or add features without accompanying test s will not be considered. 70 3. **At least one test for each bug fixed or feature added** as part of the pul l request. Pull requests that fix bugs or add features without accompanying test s will not be considered.
71 71
72 If a proposed change contains multiple commits, please [squash commits](https:// www.google.com/url?q=http://blog.steveklabnik.com/posts/2012-11-08-how-to-squash -commits-in-a-github-pull-request) to as few as is necessary to succinctly expre ss the change. A Polymer author can help you squash commits, so don’t be afraid to ask us if you need help with that! 72 If a proposed change contains multiple commits, please [squash commits](https:// www.google.com/url?q=http://blog.steveklabnik.com/posts/2012-11-08-how-to-squash -commits-in-a-github-pull-request) to as few as is necessary to succinctly expre ss the change. A Polymer author can help you squash commits, so don’t be afraid to ask us if you need help with that!
OLDNEW

Powered by Google App Engine
This is Rietveld 408576698