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: CONTRIBUTING.md
+6-9Lines changed: 6 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,7 +8,7 @@ Should you run into other issues with the project, please don't hesitate to let
8
8
9
9
Pull requests containing only failing tests demonstrating the issue are welcomed and this also helps ensure that your issue won't regress in the future once it's fixed.
10
10
11
-
Documentation issues on the handlebarsjs.com site should be reported on [handlebars-site](https://github.com/wycats/handlebars-site).
11
+
Documentation issues on the [handlebarsjs.com](https://handlebarsjs.com) site should be reported on [handlebars-lang/docs](https://github.com/handlebars-lang/docs).
12
12
13
13
## Branches
14
14
@@ -93,23 +93,20 @@ You can use the following scripts to make sure that the CI job does not fail:
93
93
94
94
Before attempting the release Handlebars, please make sure that you have the following authorizations:
95
95
96
-
- Push-access to `wycats/handlebars.js`
96
+
- Push-access to `handlebars-lang/handlebars.js`
97
97
- Publishing rights on npmjs.com for the `handlebars` package
98
98
- Publishing rights on gemfury for the `handlebars-source` package
99
99
- Push-access to the repo for legacy package managers: `components/handlebars`
100
100
- Push-access to the production-repo of the handlebars site: `handlebars-lang/handlebarsjs.com-github-pages`
101
101
102
102
_When releasing a previous version of Handlebars, please look into the CONTRIBUNG.md in the corresponding branch._
103
103
104
-
Handlebars utilizes the [release yeoman generator][generator-release] to perform most release tasks.
105
-
106
104
A full release may be completed with the following:
107
105
108
106
```
109
107
npm ci
110
-
yo release
108
+
npx grunt
111
109
npm publish
112
-
yo release:publish components handlebars.js dist/components/
113
110
114
111
cd dist/components/
115
112
gem build handlebars-source.gemspec
@@ -126,13 +123,13 @@ in those places still point to the latest version
126
123
127
124
When everything is OK, the **handlebars site** needs to be updated.
128
125
129
-
Go to the master branch of the repo [handlebars-lang/handlebarsjs.com-github-pages](https://github.com/handlebars-lang/handlebarsjs.com-github-pages/tree/master)
126
+
Go to the master branch of the repo [handlebars-lang/docs](https://github.com/handlebars-lang/docs/tree/master)
130
127
and make a minimal change to the README. This will invoke a github-action that redeploys
131
128
the site, fetching the latest version-number from the npm-registry.
132
129
(note that the default-branch of this repo is not the master and regular changes are done
0 commit comments