Process

1. Request task is created and assigned.
2. Developer picks up the task.
3. Developer creates a feature branch from master and (optionally) a merge request. MR can be created at the time of review as well.
4. Developer checks out the branch: git fetch && git checkout <branch_name>
5. Developer commits their changes to the branch and pushes to the repository.
6. Developer moves the task to "Testing".
7. Tester confirms functionality and moves to "Review", creates an MR (if it was not already created) and assigns a reviewer.
8. Reviewer checks out the branch, reviews it, and pulls from master.
9. Reviewer updates package version and commits.
10. Reviewer merges feature branch to master. This action generally closes the task and deletes the feature branch.
11. Reviewer publishes a new package: npm publish
12. Reviewer then checks out downstream dependent apps (eg., square-deal-ui and/or square-deal-blog)
13. Reviewer then updates version number for package storybook-static-pages-square-deal.
14. Reviewer commits and pushes the app.

Start storybook in development mode

npm run storybook

Create an account in NPM and login from cli by running-

npm login

Build

npm run build

Add/Update components styling

The external css files(if any) of new components should be copied to lib/config/styles

Update the version in package.json

To publish the package in npm run

npm publish

For the application which will use this npm package, say, (square-deal-ui or square-deal-blog)

Must update the version number- "storybook-static-pages-square-deal":"version number". You can find the current version number in https://www.npmjs.com/package/storybook-static-pages-square-deal