sveltekit-tooling
commitizen
Our great sponsors
sveltekit-tooling | commitizen | |
---|---|---|
1 | 9 | |
1 | 2,117 | |
- | 4.6% | |
4.3 | 9.5 | |
8 months ago | 3 days ago | |
Svelte | Python | |
BSD 3-clause "New" or "Revised" 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.
sveltekit-tooling
-
SvelteKit Tooling: 7 Tools to Streamline you CI Workflow
You can see an example project with all of this set up on the Rodney Lab Git Hub repo.
commitizen
-
What is the relation between commitizen-tools/commitizen and commitizen/cz-cli?
I followed some instruction in it and realized this tool is only for javascript projects.. While I was considering commitizen is not for me, I ran into this project: https://github.com/commitizen-tools/commitizen
-
Your Git Commit History Should Read Like a History Book. Here’s How.
Relevant to this discussion is perhaps pre-commit as it simplifies sharing git hooks which would otherwise not be tracked in git, as well as commitizen which enforces conventional commits.
-
Life is Too Short to Review Spaces
commitizen makes sure our commit messages meet our company requirements, which is a format derived from semantic-release where we require to also put the related GitLab issue’s number. Here is an example of a valid GitGuardian commit message:
-
Modern Python setup for quality development
repos: - repo: https://github.com/pre-commit/pre-commit-hooks rev: v4.0.1 hooks: - id: check-added-large-files - id: check-ast - id: check-builtin-literals - id: check-case-conflict - id: check-docstring-first - id: check-executables-have-shebangs - id: check-json - id: check-merge-conflict - id: check-symlinks - id: check-toml - id: check-vcs-permalinks - id: check-xml - id: check-yaml args: [--allow-multiple-documents] - id: debug-statements - id: detect-aws-credentials args: [--allow-missing-credentials] - id: destroyed-symlinks - id: end-of-file-fixer - id: fix-byte-order-marker - id: fix-encoding-pragma args: [--remove] - id: forbid-new-submodules - id: mixed-line-ending args: [--fix=auto] - id: name-tests-test args: [--django] - id: requirements-txt-fixer - id: trailing-whitespace - repo: local hooks: - id: black name: black entry: poetry run black language: system types: [python] - id: flake8 name: flake8 entry: poetry run flake8 language: system types: [python] - repo: https://github.com/pycqa/isort rev: "5.9.1" hooks: - id: isort args: - --profile - black - --filter-files - repo: https://github.com/adrienverge/yamllint.git rev: v1.26.1 hooks: - id: yamllint args: [-c=.yamllint.yaml] - repo: https://gitlab.com/devopshq/gitlab-ci-linter rev: v1.0.2 hooks: - id: gitlab-ci-linter args: - "--server" - "https://your.gitlab.server" # Need env var GITLAB_PRIVATE_TOKEN with gitlab api read token - repo: https://github.com/commitizen-tools/commitizen rev: v2.17.11 hooks: - id: commitizen stages: [commit-msg] - repo: https://github.com/jumanjihouse/pre-commit-hooks rev: 2.1.5 # or specific git tag hooks: - id: forbid-binary - id: shellcheck - id: shfmt
-
How to enforce git commit messages longer than stupid shit like "abc" and "fix"?
While I agree with others, that this is not strictly a technical problem I think commitizen will let you do this, among other things.
-
SvelteKit Tooling: 7 Tools to Streamline you CI Workflow
Following the type of commit in brackets we have a description for the part of the project affected. Then the commit message itself. The emoji is not required! If you want to try out conventional commits, you might like the commitizen command line tool. As well as holding your hand as you write commit messages, it can handle version bumping and generate changelogs for you. We won't go into details here, but definitely try it on a new side project to see if it suits you.
-
Semantic Versioning In Python With Git Hooks
--- repos: - repo: https://github.com/commitizen-tools/commitizen rev: master hooks: - id: commitizen stages: [commit-msg]
-
Automated version number for embedded software
Look into git flow + commitizen + semver. Git flow is secondary to your problem but is a nice to have feature. commitizen allows you to automatically bump versions based on your git commits. Look at this issue here https://github.com/commitizen-tools/commitizen/issues/358 Yes, that is me. I did say, I was grappling with the same issue a while ago..
-
Anyone know of a utility for generating commit messages?
While not a direct answer, have a look at https://github.com/commitizen-tools/commitizen
What are some alternatives?
language-tools - The Svelte Language Server, and official extensions which use it
poetry-dynamic-versioning - Plugin for Poetry to enable dynamic versioning based on VCS tags
SveltePress - Documentation for humans.
pre-commit-hooks - git pre-commit hooks that work with http://pre-commit.com/
sveltekit-tailwind-starter - A barebones starter kit for SvelteKit and TailwindCSS that includes: TypeScript, Prettier, ESLint, PostCSS, and SASS.
pre-commit - A framework for managing and maintaining multi-language pre-commit hooks.
ikon - An app for building downloadable custom sprite sheets from dragged-and-dropped directories
semantic-versioning-in-python-with-git-hooks
Beatbump - Alternative YouTube Music frontend built with Svelte/SvelteKit 🎧
cz-cli - The commitizen command line utility. #BlackLivesMatter
language-tools - ⚡ High-performance Vue language tooling based-on Volar.js
python-semver - Python package to work with Semantic Versioning (https://semver.org/)