Update CONTRIBUTING to reflec the latest changes to the deploy process

Author: antoinegrant

CONTRIBUTING.md

@@ -19,23 +19,40 @@ _Note: replace "your-username" with your GitHub handle_
 Install all package dependencies and link local packages:
 
 ```
-yarn bootstrap
+theme-scripts $ yarn bootstrap
 ```
 
 Write some features. Run the tests with:
 
 ```
-yarn test
+theme-scripts $ yarn test
 ```
 
+## Linking a new themes package with Lerna
+
+Adding dependency to all packages
+
+```
+theme-scripts $ yarn lerna add [package-name]
+```
+
+Adding dependency to a specific package
+
+```
+theme-scripts $ yarn lerna add [package-name] --scope=@shopify/theme-[name]
+```
+
+_Note: See the [lerna documentation](https://github.com/lerna/lerna/tree/2.x#add) for more information_
+
 ## How to test locally
 
 The following details how to setup your local environment when you wish to create a new branch of a theme script package. It uses work on a new release of `@shopify/themes-a11y` as an example.
 
 ### Create a link to your local package to another project
+
 Navigate to the package and type [`yarn link`](https://yarnpkg.com/en/docs/cli/link).
 
-``` bash
+```bash
 theme-scripts $ cd packages/themes-a11y
 theme-a11y $ yarn link
 
@@ -45,27 +62,26 @@ theme-a11y $ yarn link
 
 Go to a local project you want to test out the script in.
 
-``` bash
+```bash
 cd ../some-path/my-theme
 my-theme $ yarn link "@shopify/theme-a11y"
 
 # success Using linked package for "@shopify/theme-a11y".
 ```
 
-
 ### Removing a link to a package
 
-To unlink your package so other local projects stop using it, use [`yarn unlink`](https://yarnpkg.com/en/docs/cli/unlink).  This is also called “unregistering” the package.
+To unlink your package so other local projects stop using it, use [`yarn unlink`](https://yarnpkg.com/en/docs/cli/unlink). This is also called “unregistering” the package.
 
-``` bash
+```bash
 theme-a11y $ yarn unlink
 
 # success Unregistered "@shopify/theme-a11y".
 ```
 
 When you don’t want your project to be using your local package, go to your local project and type `yarn unlink <package>`
 
-``` bash
+```bash
 cd ../projects/my-theme
 my-theme $ yarn unlink "@shopify/theme-a11y"
 
@@ -80,55 +96,65 @@ functionality, changing the return value of a function, etc),
 please ensure the documentation is also updated to
 reflect this.
 
-## Changelog
-
-The changelog is updated by the repo's maintainers since a [personal access token](https://github.com/settings/tokens) with repository access is needed to handle GitHub's API call limits.
-
-If this is your first time generating changelog entries, add your personal access token with `public_repo` privileges to the `GITHUB_AUTH` environment variable by adding the following to your `.bashrc` file:
-
-```
-# Lerna Changelog Personal Access Token for shopify/theme-scripts repo
-export GITHUB_AUTH=your_personal_access_token
-```
-
-_Note: replace "your_personal_access_token" with your GitHub personal access token_
-
-Run the changelog generator:
-
-```
-npm run changelog
-```
-
-If nothing appears, you may not have any PRs tagged with appropriate labels in this release or you may have already published those changes. If you just released `v0.12.1` and the previous version was `v0.12.0`, run the following command to get the changes since `v0.12.0`:
-
-```
-npm run changelog -- --tag-from=v0.12.0
-```
-
-Copy the generated markdown from your terminal into [CHANGELOG.md](https://github.com/Shopify/theme-scripts/blob/master/CHANGELOG.md) and add any additional comments you wish to include. If the title of the autogenerated changelog is `Unreleased`, make sure you change it the new version name.
-
-Commit the changes directly to `master` branch, with a commit title of:
-
-```
-Changelog vX.X.X
-```
-
-_Note: replace "X.X.X" with new repo version number_
-
-Finally, paste the updates you made to the changelog in the release tag notes, see example: [v0.10.0 tag notes](https://github.com/Shopify/theme-scripts/releases/tag/v0.10.0).
-
 ## Publishing
 
-1. Merge any changes you want to include in your next release into `master`.
-
-_Note: If you are merging multiple PRs into `master` with a single PR (e.g. you are merging a working branch called v0.11.0 with multiple fixes made from multiple PRs into `master`), then **do not squash and merge this PR** because you will loose valuable details in the auto generated changelog_
+⚠️ Note: You must have a Shopify Okta account ir order to login to Shipit and publish.
 
-2. Update the [CHANGELOG.md](https://github.com/Shopify/theme-scripts/blob/master/CHANGELOG.md) as described above
-
-3. To select a new version number, and publish packages to NPM, run:
-
-```
-npm run publish
-```
+1. Merge any changes you want to include in your next release into `master`.
 
-_Note: Make sure you are logged into your Shopify NPM account before publishing_
+   _Note: If you are merging multiple PRs into `master` with a single PR (e.g. you are merging a working branch called v0.11.0 with multiple fixes made from multiple PRs into `master`), then **do not squash and merge this PR** because you will loose valuable details in the commit history_
+
+2. Checkout `master` and pull the latest from the origin
+
+   ```
+   theme-scripts $ git checkout master && git pull origin master
+   ```
+
+3. You can verify that there are indeed packages to be published (optional)
+
+   ```
+   theme-scripts $ yarn lerna updated
+   ...
+   lerna info version 2.11.0
+   lerna info Checking for updated packages...
+   lerna info Comparing with v2.0.4.
+   lerna info Checking for prereleased packages...
+   lerna info result
+   - @shopify/theme-a11y // This package was updated and can be published
+   ✨Done in 0.63s.
+   ```
+
+4. Run the release step to choose the version bump desired
+
+   ```
+   theme-scripts $ yarn release
+   ...
+   lerna info version 2.11.0
+   lerna info current version 2.0.4
+   lerna info Checking for updated packages...
+   lerna info Comparing with v2.0.4.
+   lerna info Checking for prereleased packages...
+   ? Select a new version (currently 2.0.4) (Use arrow keys)
+   ❯ Patch (2.0.5)
+   Minor (2.1.0)
+   Major (3.0.0)
+   Prepatch (2.0.5-0)
+   Preminor (2.1.0-0)
+   Premajor (3.0.0-0)
+   Prerelease
+   Custom
+   ```
+
+   This command will:
+
+   1. Run the equivalent of lerna updated to determine which packages need to be published.
+   2. If necessary, increment the version key in lerna.json.
+   3. Update the package.json of all updated packages to their new versions.
+   4. Update all dependencies of the updated packages with the new versions, specified with a caret (^).
+   5. Create a new git commit and tag for the new version.
+   6. Git push to origin master with the newly created tag.
+
+   _Note: See the [lerna documentation](https://github.com/lerna/lerna/tree/2.x#publish) for more information_
+
+5. Login to [Shipit](https://shipit.shopify.io/shopify/theme-scripts/production)
+6. In the Undeployed Commits list, identify the commit with the name of the version that was created in step #4, wait for CI to be 🍏, click the 'Deploy' button to publish to npm's public registry.