gitflow
release-please
Our great sponsors
gitflow | release-please | |
---|---|---|
133 | 46 | |
26,516 | 4,125 | |
- | 7.6% | |
0.0 | 8.6 | |
about 2 months ago | 6 days ago | |
Shell | TypeScript | |
GNU General Public License v3.0 or later | 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.
gitflow
-
FeiFlow - An Opinioned Git Branching And Release Management Strategy
1. GitFlow
-
Git Branches as a Social Construct
Pull Requests (or Merge Requests) are merged only when (1) all of the automated tests pass; and (2) enough necessary reviewers have indicated approval.
Git doesn't tell you when it's necessary to have full test coverage and manual infosec review in development cycles that produce releases, and neither do Pull Requests.
https://westurner.github.io/hnlog/#comment-19552164 ctrl-f hubflow
It looks like datasift's gitflow/hubflow docs are 404'ing, but the original nvie blog post [1] has the Git branching workflow diagrams; which the wpsharks/hubflow fork [3] of datasift/gitflow fork [2] of gitflow [1]has a copy of in the README:
[1] https://github.com/nvie/gitflow
[2] https://github.com/datasift/gitflow
[3] https://github.com/wpsharks/hubflow?tab=readme-ov-file
https://learngitbranching.js.org/ is still a great resource, and it could work on mobile devices.
The math of VCS deltas and mutable and immutable content-addressed DAG nodes identified by 2^n bits describing repo/$((2*inf)) bits ;
>> "ugit – Learn Git Internals by Building Git in Python" https://www.leshenko.net/p/ugit/
SLSA.dev is a social construct atop e.g. git, which is really a low-level purpose-built tool and Perl and now Python porcelain.
jj (jujutsu) is a git-compatible VCS CLI: https://github.com/martinvonz/jj
"Ask HN: Best Git workflow for small teams" (2016)
-
"Мобильная" разработка. [Системы контроля версий, Git]
A successful Git branching model - известная модель ветвления от Vincent Driessen.
- A successful Git branching model (2010)
-
Moving Fast: A Retrospective on Trunk-based Development
Before embarking on the project, we needed to decide on our Git workflow. Having experienced the unnecessary indirection and bureaucracy of Gitflow, I immediately proposed and implemented a trunk-based strategy instead.
-
Setting up GitHub Actions to deploy your website via FTP
As a best practice, consider creating a dev branch where you can stage your code and collaborate with other developers on your team. Alternatively, you can follow the Trunk-based development branching strategy. For larger teams and complex deployment cycles, the Gitflow branching model might be more suitable.
- Gitflow and GitHub Flow Compared
-
How do you use Git?
Note - this IS NOT Git Flow, which is way too complicated for what we're doing. Even the person who created Git Flow has some warnings and thoughts about it, 10 years later (https://nvie.com/posts/a-successful-git-branching-model/).
-
What strategy are you using versioning firmware with hardware in a VCS?
just use Gitflow
-
Adding @since tag when you don't know
Git and this: https://nvie.com/posts/a-successful-git-branching-model/
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?
argocd-example-apps - Example Apps to Demonstrate Argo CD
semantic-pull-requests - :robot: Let the robots take care of the semantic versioning
laragon - Laragon is a portable, isolated, fast & powerful universal development environment for PHP, Node.js, Python, Java, Go, Ruby. It is fast, lightweight, easy-to-use and easy-to-extend.
cz-cli - The commitizen command line utility. #BlackLivesMatter
semver - Semantic Versioning Specification
commitizen - Create committing rules for projects :rocket: auto bump versions :arrow_up: and auto changelog generation :open_file_folder:
git-plan - Git Plan - a better workflow for git
conventional-changelog - Generate changelogs and release notes from a project's commit messages and metadata.
GitVersion - From git log to SemVer in no time
semantic-release - :package::rocket: Fully automated version management and package publishing
metacpan-web - Web interface for MetaCPAN
semantic-pull-requests