README.md in gitlab-styles-9.1.0 vs README.md in gitlab-styles-9.2.0

- old
+ new

@@ -78,17 +78,10 @@ ```shell lefthook install ``` -## Contributing - -Bug reports and merge requests are welcome on GitLab at -https://gitlab.com/gitlab-org/gitlab-styles. This project is intended to be a -safe, welcoming space for collaboration, and contributors are expected to adhere -to the [Contributor Covenant](http://contributor-covenant.org) code of conduct. - ## Release Process We release `gitlab-styles` on an ad-hoc basis. There is no regularity to when we release, we just release when we make a change - no matter the size of the change. @@ -96,12 +89,20 @@ To release a new version: 1. Create a Merge Request. 1. Use Merge Request template [Release.md](https://gitlab.com/gitlab-org/ruby/gems/gitlab-styles/-/blob/master/.gitlab/merge_request_templates/Release.md). 1. Follow the instructions. -1. A new gem version is [published automatically](https://gitlab.com/gitlab-org/quality/pipeline-common/-/blob/master/ci/gem-release.yml) after the Merge Request has been merged. +1. (Optional, but appreciated) Create an MR on `gitlab-org/gitlab` project [with the `New Version of gitlab-styles.md` template](https://gitlab.com/gitlab-org/gitlab/-/blob/master/.gitlab/merge_request_templates/New%20Version%20of%20gitlab-styles.md) to test the new version of `gitlab-styles`, and follow the MR instructions. +1. After the Merge Request has been merged, a new gem version is [published automatically](https://gitlab.com/gitlab-org/quality/pipeline-common/-/blob/master/ci/gem-release.yml) See [!123](https://gitlab.com/gitlab-org/ruby/gems/gitlab-styles/-/merge_requests/123) as an example. + +## Contributing + +Bug reports and merge requests are welcome on GitLab at +https://gitlab.com/gitlab-org/gitlab-styles. This project is intended to be a +safe, welcoming space for collaboration, and contributors are expected to adhere +to the [Contributor Covenant](http://contributor-covenant.org) code of conduct. ## License The gem is available as open source under the terms of the [MIT License](http://opensource.org/licenses/MIT).