You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: packages/uikit-workshop/.github/CONTRIBUTING.md
+4-4
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,6 @@
1
1
# Contributing to the Default Pattern Lab Front End
2
-
If you'd like to contribute to the default frontend for Pattern Lab Node, please do so! There is always a lot of ground to cover and something for your wheelhouse.
2
+
3
+
If you'd like to contribute to the default front end for Pattern Lab Node, please do so! There is always a lot of ground to cover and something for your wheelhouse.
3
4
4
5
## Developing Locally
5
6
@@ -12,7 +13,7 @@ The best way to make changes to this repo and test them is through your existing
12
13
*`npm install`
13
14
*`npm link`
14
15
*`cd /path/to/your/edition`
15
-
*`npm link @pattern-lab/uikit-default`
16
+
*`npm link @pattern-lab/uikit-workshop`
16
17
17
18
## Making Changes
18
19
@@ -29,12 +30,11 @@ At this point changes to the static assets should compile to the correct locatio
29
30
## Guidelines
30
31
31
32
* Pattern Lab uses a standard [git flow model](http://nvie.com/posts/a-successful-git-branching-model/) unless otherwise noted in a repository. The `develop` branch is not considered stable. Tags and releases are cut from the `master` branch
32
-
*_USUALLY_ submit pull requests against the [develop branch](https://github.com/pattern-lab/uikit-default/tree/dev). If you have a major feature to stabilize over time, open an issue about making a dedicated `feature-branch` off of `develop`
33
+
*_USUALLY_ submit pull requests against the [develop branch](https://github.com/pattern-lab/uikit-workshop/tree/dev). If you have a major feature to stabilize over time, open an issue about making a dedicated `feature-branch` off of `develop`
33
34
* Please keep your pull requests concise and limited to **ONE** substantive change at a time. This makes reviewing and testing so much easier.
34
35
* Commits should reference the issue you are adressing.
35
36
* Large enhancements should begin with opening an issue. This will result in a more systematic way for us to review your contribution and determine if a [specifcation discussion](https://github.com/pattern-lab/the-spec/issues) needs to occur.
36
37
37
38
## Coding style
38
39
39
40
* The `.editorconfig` controls spaces / tabs within supported editors. Check out their [site](http://editorconfig.org/).
0 commit comments