-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
HL-930: Release Please docs and git hook & CI modifications #2242
Conversation
76e4fe0
to
034b182
Compare
* Pull request title should include Jira handle (for Jira integration to work) | ||
* Release Please figures out how much to increase the version number based on commit messages. Look [SemVer](https://semver.org/) and [Release Please docs](https://github.com/googleapis/release-please#how-should-i-write-my-commits). | ||
|
||
### Example workflow |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What do you think, is this kind of workflow something that could work for us?
branches: [main] | ||
pull_request: | ||
paths: | ||
- '.github/workflows/conventional-commits.yml' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
tarkoitus on varmaan ajaa tämä workflow aina kun pr:aan lisätään commit? Tämä taitaa nyt ajaa vain jos tulee muutos tähän filuun?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Meidän muissa workfloweissa on tuota viljelty, mutta nyt kun manuskaa tarkemmin katsoo niin eipä siinä kovin järkeä näytä olevan.
Run husky & lint-staged hooks with pre-commit. Add commitlint pre-commit hook.
Description ✨