gitignore.io
gitflow
gitignore.io | gitflow | |
---|---|---|
22 | 133 | |
8,106 | 26,540 | |
1.0% | - | |
1.9 | 0.0 | |
3 months ago | 3 months ago | |
Swift | Shell | |
MIT License | 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.
gitignore.io
- "Мобильная" разработка. [Системы контроля версий, Git]
- gitignore.io
-
Old ASP.NET/.NET Framework 3.5 gitignore question: Which files/folders should be gitignored?
gitignore.io ( https://www.toptal.com/developers/gitignore/ )
- Helpful Tool to Create .gitignore Files
-
Github installation for my Unity 2d mobile game
gitignore.io is a good start. Type in Unity and whatever editor and operating system your team is using. That should get you set up for the editor side of things.
-
Just got a new M2 Pro after my 2016 became outdated. What are your first steps to setting up a new computer?
Add global gitignore for Xcode project files and others. https://www.toptal.com/developers/gitignore
-
I just released gitignore.nvim, a .gitignore-file generator for Neovim!
That's very clever! I use this service to generate it for different editors and languages and it would just end up being an eye sore.
- What files from an Swift project should be included in a gitignore file?
-
Migrations, git and gitignore
On the topic of gitignore files, Github has example files. Another site I found useful is this
-
Git Ignore/Gradle
There are useful shared .gitignore files online in resources like this one and this one. Usually I start with the second one and then season to taste as needed.
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?
docz - ✍ It has never been so easy to document your things!
argocd-example-apps - Example Apps to Demonstrate Argo CD
Puppy - A flexible logging library written in Swift
release-please - generate release PRs based on the conventionalcommits.org spec
SendinBlueMailer - Email services powered by SendinBlue for Vapor apps
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.
ezinnit - ezinnit initializes your gitlab repository and your server. Your app will be live and commits to main will automatically deploy.
semver - Semantic Versioning Specification
ensure-gitignore - Ensure the presence of patterns within a project's gitignore
git-plan - Git Plan - a better workflow for git
ama - Ask me anything!
GitVersion - From git log to SemVer in no time