Skip to content

Commit cc7622b

Browse files
committed
📖 DOC: New Workflow
1 parent 1adce92 commit cc7622b

1 file changed

Lines changed: 13 additions & 0 deletions

File tree

‎CONTRIBUTING.md‎

Lines changed: 13 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -41,3 +41,16 @@ First of all, I'd like to welcome you for thinking about contributing to this pr
4141
### 🌟 Always use Emoji Log Messages
4242

4343
What is that? I like emoji and I have invented a way to keep the git log clean and simple. Read this [Emoji-log](https://github.com/ahmadawais/Emoji-Log) to learn more.
44+
45+
### 🎯 New Workflow
46+
47+
There's a new workflow for core developers of `create-guten-block`.
48+
49+
- Git Clone `git clone https://github.com/ahmadawais/create-guten-block/`
50+
- You need to have both `yarn` and `npm` then run `yarn` in the root of `create-guten-block` folder
51+
- You also need publishing access to all the `npm` packages in CGB so ask for that from @AhmadAwais
52+
- Now create your branch `git checkout -b githubname/feaure` and commit all changes in it
53+
- Then publish all changes as `canary` changes which are not distrubted to production sites and are meant for testing while developing `npm` packages.
54+
- To publish canary package run `npm run releaseCanary` type `y` to confirm
55+
- Now you can test changes by using `-c` or `--canary` flag `npx create-guten-block blockName -c`
56+
- I recommend that you run the latest `create-guten-block` CLI if you changed anything there. You can do that by installing the latest `create-guten-block` that you published as canary e.g. `npx create-guten-block@1.12.0-alpha.148a0211 -c blockName`

0 commit comments

Comments
 (0)