GitHub Changelog Generator
action-semantic-pull-request
Our great sponsors
| GitHub Changelog Generator | action-semantic-pull-request | |
|---|---|---|
| 3 | 5 | |
| 7,291 | 832 | |
| 0.2% | - | |
| 6.5 | 4.8 | |
| about 1 month ago | 15 days ago | |
| Ruby | JavaScript | |
| MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
GitHub Changelog Generator
-
Closing a Knowledge Gap: Best Practices for Writing Git Commit Messages
changelog-generator
-
How to Write a Great Git Commit Message
Interesting, I've been using github-changelog-generator [1] for (you guessed it) automatic changelog generation, which adds bug fixes/features to the changelog based on issues and PRs, but sematic-release looks like it might be even more useful.
[1] https://github.com/github-changelog-generator/github-changel...
- Git-cliff: generate changelog files from the Git history
action-semantic-pull-request
-
How do you link commits to tickets ?
Here you go: https://github.com/amannn/action-semantic-pull-request
-
py-template: one-click extensive GitHub Actions pipelines for your Python projects!
I am not too familiar with GitLab, to be honest, but: - Commit/PR linting (to be in tandem with semantic versioning) is implemented via third-party GitHub Actions (https://github.com/amannn/action-semantic-pull-request and https://github.com/wagoid/commitlint-github-action), these might be hard to transfer - Blocking egress to mitigate supply chain attacks is performed by step security’s Harden Runner (https://github.com/step-security/harden-runner), you may raise a question there about GitLab support - CodeQL support is GitHub only AFAIK (but you would have to verify it)
-
Microservices Shared Libraries — Design and Best Practices
There are many great tools to help with automation here, some of them are action-semantic-pull-request to enforce conventional commits and standard version to bump the version and create a changelog according to the conventional commits.
-
How to Write a Great Git Commit Message
+1 on conventional commits (big fan)
also, +1 on fully paved road approach!
You might want to check out this GitHub Action to enforce PR title matches the spec: https://github.com/amannn/action-semantic-pull-request
-
How to lint PRs and welcome contributors using GitHub Actions
amannn/[email protected] - ensures pull request title matches conventional commits specification
What are some alternatives?
Asciidoctor - :gem: A fast, open source text processor and publishing toolchain, written in Ruby, for converting AsciiDoc content to HTML 5, DocBook 5, and other formats.
conventional-commit - commit binary powered by commitizen with conventional commit standard
grape-swagger - Add OAPI/swagger v2.0 compliant documentation to your grape API
semantic-release - :package::rocket: Fully automated version management and package publishing
Annotate - Annotate Rails classes with schema and routes info
commit-analyzer - :bulb: semantic-release plugin to analyze commits with conventional-changelog
YARD - YARD is a Ruby Documentation tool. The Y stands for "Yay!"
commit-emoji - Performs a git commit with a random emoji message. 😂 🤙 🚀
Hanna - RDoc generator designed with simplicity, beauty and ease of browsing in mind
pr-compliance-action - Check PR for compliance on title, linked issues, and files changed
Doctor
github-changel