Giters
octue
/
conventional-commits
Continuous deployment via Conventional Commits
Geek Repo:
Geek Repo
Github PK Tool:
Github PK Tool
Stargazers:
4
Watchers:
2
Issues:
40
Forks:
0
octue/conventional-commits Issues
Remove old scripts
Closed
a year ago
Ignore commit header line length limit if commit code is `MRG`
Closed
a year ago
TypeError on a PR with many commits
Updated
a year ago
Comments count
2
Implement a set of Github Actions
Closed
2 years ago
Remove line length limit for commit bodies or format it away so upgrade instructions render nicely in markdown
Closed
2 years ago
Improve upgrade instructions format in release notes generator
Closed
2 years ago
I want a boom
Closed
2 years ago
Consider merging some of the release notes sections
Updated
2 years ago
Add breaking change commit notes to release notes
Closed
2 years ago
Comments count
3
Write article on the benefits of conventional-commit-based continuous deployment on Medium for the new website
Updated
2 years ago
Comments count
1
Consider using ❌ or similar emoji to denote breaking changes
Closed
2 years ago
Comments count
4
BREAKING-CHANGES has a mismatched format
Closed
2 years ago
Comments count
1
Allow brackets at end of commit message
Closed
2 years ago
Consider putting all breaking changes at top of their sections in release notes generator
Updated
2 years ago
Add commit codes for deprecation and subsequent removal
Closed
2 years ago
Comments count
3
Add support for `DEPRECATION` notes in commits
Updated
2 years ago
Add whitespace to valid commit header endings
Closed
2 years ago
Add style subheading to release notes
Closed
2 years ago
Missing commits from PR history
Closed
3 years ago
Allow quotation marks at end of commit headers
Closed
3 years ago
Mkver comparison incorrect where package.json not in repository root
Closed
3 years ago
Comments count
3
Add option to add link to relevant pull request in release notes
Closed
3 years ago
Link release note items to commit diff
Updated
3 years ago
Support commits with multi-line bodies
Closed
3 years ago
Indicate in release notes what breaking changes have taken place
Closed
3 years ago
Release notes not generating on GitHub on some repositories but are locally
Closed
3 years ago
Document semantic version checker / provide examples
Closed
3 years ago
Comments count
1
Semver checker fails due to branch name inclusion
Closed
3 years ago
Comments count
3
Raise an error if mkver.conf isn't present
Closed
3 years ago
Allow semver checking against a monorepo package or git submodule
Closed
3 years ago
Pretty-Print available versions
Closed
3 years ago
Add VER: prefix?
Closed
3 years ago
Comments count
3
Always compares to main branch
Closed
3 years ago
Comments count
5
Strange merge commits always appear in release notes
Closed
3 years ago
Extra colons interfere with commit classfications
Closed
3 years ago
Test rest of package
Closed
3 years ago
update-pull-request action failing
Closed
3 years ago
Unhide the default prefix list in the readme
Closed
3 years ago
Conventional Commits
Closed
3 years ago
Comments count
9