git-assembler can perform automatic merge and rebase operations following a simple declarative script. Like “make”, for branches. It can be used to follow remote branches (such as pull requests) conveniently, test multiple patches together, work on interdependent feature branches more easily, and so on…

GitLab 13.1.2

GitLab is a development collaboration tool and git DVCS frontend. It includes repository management features, code reviews, an issue tracker, activity feeds and wikis. GitLab provides fine-grained access control, user management, 5 permission levels and branch constraints, and can utilize LDAP/AD intranet authorization. Powered by Ruby on Rails it comes as open source package, and as commercial supported enterprise version.

Gitea 1.12.1

Gitea is a painless self-hosted Git service. It is similar to GitHub, Bitbucket, and GitLab. Gitea is a fork of Gogs. See the Gitea Announcement blog post to read about the justification for a fork. Purpose The goal of this project is to provide the easiest, fastest, and most painless way of setting up a self-hosted Git service. With Go, this can be done with an independent binary distribution across all platforms and architectures that Go supports. This support includes Linux, macOS, and Windo

git 2.27.0 💾

Git is a distributed version control system, originally designed for Linux kernel development and large projects with non-linear workflows. It's comprised of individual tools, reuses ssh and rsync protocols, emphasises speed and data integrity, and keeps every checkout as full-fledged repository, and cryptographically authenticates source history. Various graphical frontends, IDE integrations and web services (GitHub) exist; with its git-fast-export format meanwhile serves interoperability with

minor feature: When "git describe C" finds that commit C is pointed by a signed or, annotated tag, which records T as its tagname in the object, the, command gives T as its answer. Even if the user renames or moves, such a tag from its natural location in the "refs/tags/" hierarchy, "git describe C" would still give T as the answer, but in such a, case "git show T 0" would no longer work as expected. There may be, nothing at "refs/tags/T" or even worse there may be a different tag, instead. Starting from this version, "git describe" will always use the, "long" version, as if the "--long" option were given, when giving, its output based on such a misplaced tag to work around the problem. "git pull" a warning message until the pull.rebase, configuration variable is explicitly given, which some existing, users may find annoying---those who prefer not to rebase need to, set the variable to false to squelch the warning. The transport protocol version 2, which was promoted to the default, in Git 2.26 release, turned out to have some remaining rough edges, so it has been demoted from the default. A handful of options to configure SSL when talking to proxies have, been added. Smudge/clean conversion filters are now given more information, (e.g. the object of the tree-ish in which the blob being converted, appears, in addition to its path, which has already been given). When "git describe C" finds an annotated tag with tagname A to be, the best name to explain commit C, and the tag is stored in a, "wrong" place in the refs/tags hierarchy, e.g. refs/tags/B, the, command gave a warning message but used A (not B) to describe C. If C is exactly at the tag, the describe output would be "A", but, "git rev-parse A 0" would not be equal as "git rev-parse C 0". The, behavior of the command has been changed to use the "long" form, i.e. A-0-gOBJECTNAME, which is correctly interpreted by rev-parse. "git pull" learned to warn when no pull.rebase configuration, exists, and neither -- no- rebase no

GNU LGPL c git scm vcs dvcs

Git LFS 2.11.0

Git Large File Storage (LFS) replaces large files such as audio samples, videos, datasets, and graphics with text pointers inside Git, while storing the file contents on a remote server like or GitHub Enterprise.

BashStyle-NG 10.7.1

BashStyle-NG is a graphical tool and toolchain for changing the behaviour and look'n'feel of Bash, Readline, Vim, Nano and Git. Possibilities include Bash: 12 fancy pre-defined prompt styles, colors are customizable, random text color, random prompt style for each session possible, create your own prompt using UI, colored manpages (without using most), rembering last visited directory (and restore upon new session), customize bash history settings, lscd: customized variant of cd, showing conte

git-annex 7.20191009

git-annex allows managing files with git, without checking the file contents into git. While that may seem paradoxical, it is useful when dealing with files larger than git can currently easily handle, whether due to limitations in memory, checksumming time, or disk space. Even without file content tracking, being able to manage files with git, move files around and delete files with versioned directory trees, and use branches and distributed clones, are all very handy reasons to use git. And a

QtPass 1.3.2

Password management should be simple and follow Unix philosophy. With QtPass, each password lives inside of a gpg encrypted file whose filename is the title of the website or resource that requires the password. These encrypted files can be be organised into meaningful folder hierarchies, which can be shared with teams.

GitZone 1.1

GitZone is a Git DNS zone file management tool for BIND9. Users can update their zones in a git repository then during a push the zone files are checked, updated & reloaded from git receive hooks. If there’s an error in a file being pushed then the push is rejected, thus only correct files are stored on the server. GitZone-shell is similar to git-shell but it restricts the user to the zones repository and provides some additional commands for dynamic DNS updates & SSH key management.

multi-git-status 1.0

Multi-git-status shows uncommited, untracked, unpushed and unpulled changes in multiple Git repositories.