Superface CLI
release-please
Superface CLI | release-please | |
---|---|---|
2 | 47 | |
21 | 4,199 | |
- | 4.3% | |
9.1 | 8.5 | |
5 months ago | 16 days ago | |
TypeScript | TypeScript | |
MIT License | Apache License 2.0 |
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.
Superface CLI
-
Automate npm publishing with GitHub Actions, proper changelog, and release notes
You can see the workflow in action in most of our package repositories, for example OneSDK for Node.js and Superface CLI.
-
What’s new at Superface: November 2021
With the public launch, we have also released 1.0 versions of OneSDK, Superface CLI, and supporting libraries. We're committed to backwards compatibility, so you can expect our APIs to remain stable.
release-please
-
How to write GIT commit messages
Conventional Commits
-
How to Improve Development Experience of your React Project
We've covered everything about writing well-formatted and structured code without worrying too much about it anymore. The only part we haven't explored yet is linting commit messages. Commitlint will help us here. It allows you to configure any rules you want for the commit message, but we're going to use the Conventional Commits specification, one of the most popular conventions you'll find.
- Release Please
-
TypeScript Boilerplate
Commit Management with Conventional Commits: The Conventional Commits methodology is adopted to maintain a clear and structured record of changes with the help of commitlint.
-
A Gitlab Review Bot Assistant
Validate if the commit titles adhere to the Conventional Commits Specification in Merge requests.
-
Ask HN: Should commit summaries describe the change, or the intent?
Check out https://www.conventionalcommits.org
-
Announcing release-plz v0.3.0
FYI there is already a popular tool that does just this with a very similar name: https://github.com/googleapis/release-please
-
A clean Git history with Git Rebase and Conventional Commits
The feature commit should have a clear defined message - Don't re-invent here - There exists a fairly used and accepted convention called Conventional Commits, so we are going to use that.
-
Add a semver tag to release and auto increment it based on last tag
Check out https://github.com/googleapis/release-please
What are some alternatives?
OneSDK - 1️⃣ One Node.js SDK for all the APIs you want to integrate with
semantic-pull-requests - :robot: Let the robots take care of the semantic versioning
semantic-release - :package::rocket: Fully automated version management and package publishing
gitflow - Git extensions to provide high-level repository operations for Vincent Driessen's branching model.
Hoppscotch - Open source API development ecosystem.
cz-cli - The commitizen command line utility. #BlackLivesMatter
cli - Mockoon's official CLI. Deploy your mock APIs anywhere.
commitizen - Create committing rules for projects :rocket: auto bump versions :arrow_up: and auto changelog generation :open_file_folder:
conventional-changelog - Generate changelogs and release notes from a project's commit messages and metadata.
semantic-pull-requests
git-hook-conventional-commits-validator - A Git pre-commit hook which validates commit messages using Conventional Commits standard