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: README.md
+19-14Lines changed: 19 additions & 14 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -208,33 +208,38 @@ After executing this tasks you'll be able to access the documentation at [http:/
208
208
$ npm run ngdocs:view -- --port=8002
209
209
```
210
210
211
-
## Releasing
211
+
## Git Commit Guidelines
212
212
213
-
Angular PatternFly is released through Bower and npm. To release a new version version of Angular PatternFly, edit `bower.json` and `package.json` accordingly.
213
+
PatternFly uses a semantic release process to automate npm and bower package publishing, based on the following commit message format.
214
+
215
+
Each commit message consists of a **header**, a **body** and a **footer**. The header has a special
216
+
format that includes a **type**, a **scope** and a **subject** ([full explanation](https://github.com/stevemao/conventional-changelog-angular/blob/master/convention.md)):
214
217
215
-
Update the version listed in `bower.json` by editing the file and changing the line:
216
218
```
217
-
"version": "<new_version>"
219
+
<type>(<scope>): <subject>
220
+
<BLANK LINE>
221
+
<body>
222
+
<BLANK LINE>
223
+
<footer>
218
224
```
219
225
220
-
Update the patternfly reference version listed in `bower.json` by editing the file and changing the line below. Angular patternfly has a dependency on the patternfly reference implementation so the major and minor version numbers of the two project should be the same:
226
+
##### Patch Release
227
+
221
228
```
222
-
"patternfly": "<new_version>"
229
+
fix(pencil): stop graphite breaking when too much pressure applied
223
230
```
224
231
232
+
##### Feature Release
225
233
226
-
Update the version listed in `package.json` by editing the file and changing the line:
227
234
```
228
-
"version": "<new_version>"
235
+
feat(pencil): add 'graphiteWidth' option
229
236
```
230
237
231
-
Commit the version bump:
232
-
```shell
233
-
$ git commit -m "Version bump to <new_version>"
234
-
```
238
+
##### Breaking Release
235
239
236
-
Publish a new set of release notes with ```new version``` as the tag version:
0 commit comments