action-semantic-pull-request
pr-compliance-action
| action-semantic-pull-request | pr-compliance-action | |
|---|---|---|
| 5 | 2 | |
| 843 | 159 | |
| - | - | |
| 4.8 | 6.5 | |
| 7 days ago | 5 months ago | |
| JavaScript | TypeScript | |
| 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.
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
pr-compliance-action
-
How to lint PRs and welcome contributors using GitHub Actions
mtfoley/[email protected] - check PR for compliance on title, linked issues, and files changed
-
pr-compliance-action
Inspired by this need of the project, and some of the work in pr-lint-action, I managed to create and do a pre-release on pr-compliance-action, and it was implemented in the Open Sauced project last week!
What are some alternatives?
conventional-commit - commit binary powered by commitizen with conventional commit standard
first-interaction - An action for filtering pull requests and issues from first-time contributors
semantic-release - :package::rocket: Fully automated version management and package publishing
open-sauced - 🍕 This is a project to identify your next open source contribution.
commit-analyzer - :bulb: semantic-release plugin to analyze commits with conventional-changelog
foundry-gas-diff - 🛠️ Easily track & compare gas costs estimated by Foundry on each of your Pull Requests!
GitHub Changelog Generator - Automatically generate change log from your tags, issues, labels and pull requests on GitHub.
commit-emoji - Performs a git commit with a random emoji message. 😂 🤙 🚀
pr-lint-action - :octocat: A fast 🔥 TypeScript GitHub Action to ensure that your PR title matches a given regex.
github-changel
setup-bun - Set up your GitHub Actions workflow with a specific version of Bun