update contribution guidelines (#734)

* Save upload-24.svg * Optimize SVGs * Create twenty-bugs-mate.md * Add note for where to commit a changeset Co-authored-by: Javier Diaz <edokoa@github.com> Co-authored-by: Javier Diaz <actions@github.com>
primer · Feb 8, 2022 · afde0dd · afde0dd
1 parent 2453967
commit afde0dd
Show file tree

Hide file tree

Showing 2 changed files with 7 additions and 0 deletions.
diff --git a/.changeset/twenty-bugs-mate.md b/.changeset/twenty-bugs-mate.md
@@ -0,0 +1,5 @@
+---
+"@primer/octicons": patch
+---
+
+Modify upload-24.svg to mirror 16px version
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
@@ -99,6 +99,8 @@ Releases are managed by 🦋 [Changesets](https://github.com/atlassian/changeset
 
 We have the [changeset-bot comment on new pull requests](https://github.com/changesets/bot#readme) asking contributors or maintainers to add a changeset file, which will become the markdown supported changelog entry for the change.
 
+When creating the changeset always commit into the working branch (pull request branch), not `main`.
+
 When a pull request is approved merge it into the `main` branch. The changeset action will then create a Release pull request that includes this new pull request.
 
 Once maintainers have agreed and are satisifed with the release. Merge the Release pull request. Changesets will then publish a new GitHub release to the repository with the changelog and new version number. A second action will be triggered by this release and publish the new versions to npm and rubygems.