kwote
action-semantic-pull-request
| kwote | action-semantic-pull-request | |
|---|---|---|
| 2 | 5 | |
| 54 | 852 | |
| - | - | |
| 0.0 | 6.1 | |
| over 1 year ago | 20 days ago | |
| TypeScript | 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.
kwote
-
How to Write a Great Git Commit Message
Honest question, do you really expect your history to be meaningful long-term? Or are you simply taking the approach that the commit message is meaningless and a developer instead use GitHub search to find a PR relevant to a change they're investigating.
For example, I pulled up one of your projects and the history (https://github.com/transitive-bullshit/kwote/commits/main) is less than meaningless, compared to i.e. using emojis as a shorthand (https://github.com/tiangolo/fastapi/commits/master)
- Show HN: Simple OSS webapp to create beautiful quotes
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?
git-plan - Git Plan - a better workflow for git
conventional-commit - commit binary powered by commitizen with conventional commit standard
commit-emoji - Performs a git commit with a random emoji message. 😂 🤙 🚀
semantic-release - :package::rocket: Fully automated version management and package publishing
rDrama - moved to https://fsdfsd.net/rDrama/rDrama
commit-analyzer - :bulb: semantic-release plugin to analyze commits with conventional-changelog
GitHub Changelog Generator - Automatically generate change log from your tags, issues, labels and pull requests on GitHub.
fastapi - FastAPI framework, high performance, easy to learn, fast to code, ready for production
Vim - The official Vim repository
pr-compliance-action - Check PR for compliance on title, linked issues, and files changed