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
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.
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: git rebase" uses a different backend that is based on the 'merge', machinery by default. There are a few known differences in the, behaviour from the traditional machinery based on patch+apply. If your workflow is negatively affected by this change, please, report it to email@example.com so that we can take a look into, it. After doing so, you can set the 'rebase.backend' configuration, variable to 'apply', in order to use the old default behaviour in, the meantime. Sample credential helper for using.netrc has been updated to work, out of the box. gpg.minTrustLevel configuration variable has been introduced to, tell various signature verification codepaths the required minimum, trust level. The command line completion (in contrib/) learned to complete, subcommands and arguments to "git worktree". Disambiguation logic to tell revisions and pathspec apart has been, tweaked so that backslash-escaped glob special characters do not, count in the "wildcards are pathspec" rule. One effect of specifying where the GIT_DIR is (either with the, environment variable, or with the "git --git-dir=. cmd", option) is to disable the repository discovery. This has been, placed a bit more stress in the documentation, as new users often, get confused. Two help messages given when "git add" notices the user gave it, nothing to add have been updated to use advise() API. A new version of fsmonitor-watchman hook has been introduced, to, avoid races. "git config" learned to show in which "scope", in addition to in, which file, each config setting comes from. The basic 7 colors learned the brighter counterparts, (e.g. "brightred"). "git sparse-checkout" learned a new "add" subcommand. A configuration element used for credential subsystem can now use, wildcard pattern to specify for which set of URLs the entry, applies. "git clone --recurse-submodules --single-branch" now uses the same, single-branch option when cloning the submodules. "git rm" and "git stash" learns the new "-
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 GitHub.com or GitHub Enterprise.
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 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
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 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.
Caja extension to add important information about the current git directory. This project is based on nautilus-git by Bilal Elmoussaoui.
Multi-git-status shows uncommited, untracked, unpushed and unpulled changes in multiple Git repositories.