sublime_merge
gitflow
sublime_merge | gitflow | |
---|---|---|
27 | 133 | |
270 | 26,525 | |
1.1% | - | |
0.0 | 0.0 | |
8 months ago | 2 months ago | |
Shell | ||
- | GNU General Public License v3.0 or later |
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.
sublime_merge
- I don't know why so many devs avoid a GUI for Git
- Sublime Merge – Git Client from the Makers of Sublime Text
- Ask HN: How to give a crash course on Git?
-
Lazygit: Simple terminal UI for Git commands
I've used this before and it is great. I mainly use Sublime Merge these days, though: https://www.sublimemerge.com/
-
Ask HN: Dev productivity tools you would pay for
Other good graphical git clients I have used in the past are Sublime Merge https://www.sublimemerge.com/ and SmartGit https://www.syntevo.com/smartgit/.
They are usually not expensive, and I learned git with GUIs.
- Top 10 Git GUI Clients for Linux in 2023
- Exploring the Top 10 Git GUI Clients for Linux in 2023
-
3 way merge tool as good as IntelliJ?
I’m in the same boat. The best I’ve come up with is sublime merge, works well but I miss the keyboard shortcuts and it being part of the editor
-
The github CLI saved me a lot of times
Even though I am pretty comfortable (or was) with git cli, I'm not going back from sublime merge
-
#gitPanic - Tools
Personally, I find it really helps me to see the repo history visualized as a tree, so I currently use Sublime Merge. I've used GitKraken and Sourcetree in the past. The git reference documentation maintains a list of git GUI clients, including mobile apps!
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/
What are some alternatives?
legit - Git for Humans, Inspired by GitHub for Mac™.
argocd-example-apps - Example Apps to Demonstrate Argo CD
git-gui - Tcl/Tk based UI for Git. I am currently acting as the project's maintainer.
release-please - generate release PRs based on the conventionalcommits.org spec
GitUp - The Git interface you've been missing all your life has finally arrived.
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.
GitExtensions - Git Extensions is a standalone UI tool for managing git repositories. It also integrates with Windows Explorer and Microsoft Visual Studio (2015/2017/2019).
semver - Semantic Versioning Specification
desktop - Fork of GitHub Desktop to support various Linux distributions
git-plan - Git Plan - a better workflow for git
terraform-provider-wireguard - Terraform provider for WireGuard metadata
GitVersion - From git log to SemVer in no time