-
Research semantic commit messages and comment your findings below this issue.
-
I received this email and documenting it GitHub to keep track of it better. I anticipate this error is from breaking changes in semantic-release and commit-analyzer.
> Hello Evelyn,
>
> First of…
-
As described here https://www.conventionalcommits.org/en/v1.0.0/
And add a changelog
-
## :rotating_light: The automated release from the `main` branch failed. :rotating_light:
I recommend you give this issue a high priority, so other packages depending on you can benefit from your bug…
-
**Checklist**
- [X] I've included the output of `alr version`.
- [X] I've included complete steps to reproduce my issue.
**Describe the bug**
I have a remote source archive (a `.tar.gz` file) …
-
## what
The module could follow a semantic versioning scheme major.minor.patch
Using semantic commits, such as
- `feat!` for breaking backwards compatibility would cause a major version bump
…
-
There is a problem in release note generator that puts wrong click up id in the `, closes [#8693y647](link/to/clickup/8693y647)` that comes end of each change item (the correct id shoud be `8693y647d`…
-
I made an update just a few days ago and now when I use the “Generate commit message with Copilot” feature, I get the messages `chore:` and `feat:` in the commit message.
I am not a fan of this featu…
-
## :rotating_light: The automated release from the `master` branch failed. :rotating_light:
I recommend you give this issue a high priority, so other packages depending on you can benefit from your b…
-
## :rotating_light: The automated release from the `main` branch failed. :rotating_light:
I recommend you give this issue a high priority, so other packages depending on you can benefit from your bug…