Open Source Linux Git Software - Page 6
Sort By:
Git Software for Linux
View 17 business solutions-
Build Securely on Azure with Proven FrameworksMoving to the cloud brings new challenges. How can you manage a larger attack surface while ensuring great network performance? Turn to Fortinet’s Tested Reference Architectures, blueprints for designing and securing cloud environments built by cybersecurity experts. Learn more and explore use cases in this white paper.
-
MongoDB Atlas runs apps anywhereMongoDB Atlas gives you the freedom to build and run modern applications anywhere—across AWS, Azure, and Google Cloud. With global availability in over 115 regions, Atlas lets you deploy close to your users, meet compliance needs, and scale with confidence across any geography.
-
1
QtcGistPlugin
GitHub Gist plugin for QtCreator
-
2
RepoZ
A zero-conf git repository hub for Windows and macOS
RepoZ is a zero-conf git repository hub with Windows Explorer- & CLI enhancements. It uses the git repositories on your machine to create an efficient navigation widget and makes sure you'll never lose track of your work along the way. It's populating itself as you work with git. It does not get in the way and does not require any user attention to work. RepoZ will not compete with your favorite git clients, so keep them. It's not about working within a repository: It's a new way to use all of your repositories to make your daily work easier. The hub provides a quick overview of your repositories including their current branch and short status information. Additionally, it offers some shortcuts like revealing a repository in the Windows Explorer or macOS Finder, opening a command line tool in a given repository and checking out git branches. -
3
Rugged
ruby bindings to libgit2
Rugged is a library for accessing libgit2 in Ruby. It gives you the speed and portability of libgit2 with the beauty of the Ruby language. libgit2 is a pure C implementation of the Git core methods. It's designed to be fast and portable. For more information about libgit2, check out libgit2's website or browse the libgit2 organization on GitHub. You need to have CMake and pkg-config installed on your system to be able to build the included version of libgit2. Note that you only need libgit2-dev if you want to build with the system libgit2 rather than the vendored version. In this case, note that the major and minor versions of libgit2 and rugged must match. By default, Rugged builds and uses a bundled version of libgit2. Rugged gives you access to the many parts of a Git repository. You can read and write objects, walk a tree, access the staging area, and lots more. Let's look at each area individually. -
4
SF Wiki Helper
Script enabling off-line preparation and version control of wiki pages
This tool is a bash script that enables off-line editing and git version control of markdown files for the standard SourceForge wiki tool. In this way you can prepare changes in documentation while working on a release and publish them at the moment your release becomes available to the public. It uses Sourceforge's Allura REST API to download and publish the wiki's markdown files. -
Keep company data safe with Chrome EnterpriseMake AI work your way with Chrome Enterprise. Block unapproved sites and set custom data controls that align with your company's policies.
-
5
SwiftPamphletApp
SwiftUI + Combine + Swift Concurrency Aysnc/Await Actor + GitHub API
Dai Ming's development brochure, a living development manual. macOS app developed with SwiftUI + Combine + Swift Concurrency Aysnc/Await Actor + GitHub API. Pull the code. Directly compile and generate a manual program without Github function. If you want to use the Github function, you can add your GitHub Access Token to gitHubAccessToken in SwiftPamphletAppConfig.swift. Get the GitHub Access Token at Personal Access Tokens here. Remember to tick repo and user in scope. Both Xcode and macOS need to be upgraded to the latest version. You can use compile.command to compile the manual program, no need to open Xcode to set up a personal development account, just add your GitHub Access Token to gitHubAccessToken in SwiftPamphletAppConfig.swift , and then click compile.command twice to wait for the job to complete. The booklet can easily view the Swift syntax, and there are some guides for the use of the main libraries. The content is still being improved. -
6
Useful Forks
Improving GitHub's Forks list discoverability through auto-filtering
It aims at increasing the discoverability of useful forks of open-source projects. Simply type a repository's URL in the Text Field. The criteria is simple: if a fork was created, but never received any other activity on its master branch, it is filtered out. Adding a sorted list of starred forks to the GitHub forks page. Results are filtered out if there were never any commits pushed on the main branch since the fork was created. This is meant to help increase the discoverability of useful forks of open-source projects. Sometimes, a project might be abandoned, or someone had a different idea of how it should be implemented... and when you go looking for those interesting forks, you find yourself searching through potentially hundreds of them. This tool is here to help you discover the hidden jewels you were looking for! -
7
VersionPress
Git-based version control for WordPress. Whoa!
VersionPress is a free and open-source plugin that brings the full power of Git to WordPress. Its key strength is that it version-controls not just files but also the database. VersionPress automatically creates Git commits for both file and database changes, in natural language. Plugins break, people make mistakes; sometimes, you just want that good old Undo button. Git took the pain out of file merging; VersionPress does the same for WP database. You can push to GitHub, your colleagues pull and make the site fully functional in seconds. MySQL is a cache. VersionPress can store hundreds of full site snapshots to just a few megabytes. We care about UX deeply. VersionPress should not be a low-level tool for geeks. It works fine on simpler sites and you're encouraged to try it in your development workflows but it is not production-ready yet. -
8
-
9
Walle 2.0
Walle 2.0 web
Support multi-project, multi-environment one-click deployment and online, one-click quick rollback. Online order application, review, deployment, and real-time operation logs. Permissions, notifications, file fingerprints. Independent space resources like gitlab. Custom environment, environment variables. Project administrator, a notification mechanism, custom hooks in each process. Get through server management, grayscale release. Advanced gitlab-like user management mode. Online order application, review, grayscale release, real-time websocket. Walle allows users to release code and finally can not only choose jenkins! Support various web code releases, release and rollback of php, java, python, go and other codes can be completed with one click through the web. walle is a freely configurable project, more user-friendly, high-value, an open source online deployment system that supports git, multi-user, multi-language, multi-project, and multi-environment simultaneous deployment. -
Simple, Secure Domain RegistrationRegister or renew your domain and pay only what we pay. No markups, hidden fees, or surprise add-ons. Choose from over 400 TLDs (.com, .ai, .dev). Every domain is integrated with Cloudflare's industry-leading DNS, CDN, and free SSL to make your site faster and more secure. Simple, secure, at-cost domain registration.
-
10
Znap!
Znap! Fast, easy-to-use tools for Zsh dotfiles & plugins
Znap is a fast, light-weight set of tools to ease the use of Zsh plugins & Git repos and reduce your shell's startup time. Using Znap to manage your plugins can be as simple as putting this in your .zshrc file. Additionally, Znap makes it so that you actually need to have less in your .zshrc file, by automating several tasks for you. Note that the above example does not include any call to complist, compinit, or bashcompinit in the .zshrc file. That is because Znap will run these for you as needed. Znap compiles your scripts and functions in the background. This way, your shell will start up even faster next time! Znap automatically regenerates your comp dump file whenever you install or update a repo or change your .zshrc file. When using git 2.31.0 or newer, Znap automatically enables git maintenance in each repo that it manages. This automatically optimizes your repos in the background, so that your git and znap commands will run faster. -
11
ANT4GIT is an ANT task for GIT, a distributed source control management system (http://git-scm.com/).
-
12
bit CLI
Bit is a modern Git CLI
bit is an experimental modernized git CLI built on top of git that provides happy defaults and other niceties. Command and flag suggestions to help you navigate the plethora of options git provides you. Autocompletion for files and branch names when using bit add or bit checkout. Automatic fetch and branch fast-forwarding reduce the likelihood of merge conflicts. Suggestions work with git aliases. New commands like bit sync vastly simplify your workflow. Commands from git-extras such as bit release & bit info. Fully compatible with git allowing you to fallback to git if need be. Get insight into how bit works using bit --debug. -
13
commitlint
Lint commit messages
commitlint checks if your commit messages meet the conventional commit format. commitlint helps your team adhere to a commit convention. By supporting npm-installed configurations it makes sharing of commit conventions easy. We're not a sponsored OSS project. Therefore we can't promise that we will release patch versions for older releases in a timely manner. If you are stuck on an older version and need a security patch we're happy if you can provide a PR. If something in between fails (like a new packages was added and needs to be published for the first time but you forgot) you can use lerna publish from-package to publish anythign that has not been published yet. We identify ease of adoption and developer experience as fields where there is room and need for improvement. The items on the roadmap should enhance commitlint regarding those aspects. -
14
composer-git-hooks
Easily manage git hooks in your composer config
Manage git hooks easily in your composer configuration. This command line tool makes it easy to implement a consistent project-wide usage of git hooks. Specifying hooks in the composer file makes them available for every member of the project team. This provides a consistent environment and behavior for everyone which is great. It is also possible to use to manage git hooks globally for every repository on your computer. That way you have a reliable set of hooks crafted by yourself for every project you choose to work on. You can also install it globally. This feels much more natural when cghooks is used with the newly added support for managing global git hooks. When a hook is a sequence of commands, it can be useful to stop the execution when a command fails. Custom hooks can be added to the custom-hooks array of the `config section. -
15
diff2html
Pretty diff to html javascript library (diff2html)
Each diff provides a comprehensive visualization of the code changes, helping developers identify problems and better understand the changes. Each diff features a line-by-line and side-by-side preview of your changes. All the code changes are syntax highlighted using highlight.js, providing more readability. Similar lines are paired, allowing for easier change tracking. We work hard to make sure you can have your diffs in a simple and flexible way. The AI community building the future. Build, train and deploy state of the art models powered by the reference open source in natural language processing. Wrapper and helper adding syntax highlight, synchronized scroll, and other nice features. You can use it without syntax highlight or by passing your own implementation with the languages you prefer. Diff2Html can be used in various ways as listed in the distributions section. -
16
exa
A modern replacement for ls
You list files hundreds of times a day. Why spend your time squinting at black and white text? exa is an improved file lister with more features and better defaults. It uses colours to distinguish file types and metadata. It knows about symlinks, extended attributes, and Git. And it’s small, fast, and just one single binary. Different types of file and data will be coloured differently, and the user and group columns will be highlighted for the current user. exa can display a file’s extended attributes, as well as standard filesystem information such as the inode, the number of blocks, and a file’s various dates and times. exa queries files in parallel, giving you performance on par with ls. Not only is the standard tree tool built-in, but it’ll show you your files’ information alongside the hierarchy. View the staged and unstaged status of every file, right there in the standard view. Also works in tree view for a high-level overview of your repository. -
17
forgit
A utility tool powered by fzf for using git interactively
This tool is designed to help you use git more efficiently. It's lightweight and easy to use. Fig adds apps, shortcuts, and autocomplete to your existing terminal. Options can be set via environment variables. They have to be exported in order to be recognized by forgit. You can use forgit as a subcommand of git by making git-forgit available in $PATH. Forgit will use the default configured pager from git (core.pager, pager.show, pager.diff) but can be altered with several environment variables. You can add default fzf options for forgit, including keybinds, layout, etc. (No need to repeat the options already defined. -
18
ghooks
Simple git hooks
Simple git hooks. It is not advised to install ghooks as a production dependency, as it will install git hooks in your production environment as well. Please install it under the devDependencies section of your package.json. Please also note, that it is absolutely not advised to install ghooks globally. To work as expected, make it a development dependency of your project(s). Add a config.ghooks entry in your package.json and simply specify which git hooks you want and their corresponding commands. The hooks' working directory is relative to the git root (where you have your .git directory). This means that if your package.json is in a subdirectory of your git repository, you'll need to cd into the directory before running any npm scripts. -
19
git absorb
git commit --fixup, but automatic
This is a port of Facebook's hg absorb. Facebook demoed hg absorb which is probably the coolest workflow enhancement I've seen to version control in years. Essentially, when your working directory has uncommitted changes on top of draft changesets, you can run hg absorb and the uncommitted modifications are automagically folded ("absorbed") into the appropriate draft ancestor changesets. This is essentially doing hg histedit + "roll" actions without having to make a commit or manually make history modification rules. The command essentially looks at the lines that were modified, finds a changeset modifying those lines, and amends that changeset to include your uncommitted changes. If the changes can't be made without conflicts, they remain uncommitted. This workflow is insanely useful for things like applying review feedback. You just make file changes, run hg absorb and the mapping of changes to commits sorts itself out. It is magical. -
20
git-auto-commit Action
Automatically Commit changed Files back to GitHub
Automatically Commit changed Files back to GitHub with GitHub Actions for the 80% use case. A GitHub Action to detect changed files during a Workflow run and to commit and push them back to the GitHub repository. By default, the commit is made in the name of "GitHub Actions" and co-authored by the user that made the last commit. Note that the Action has to be used in a Job that runs on a UNIX system (e.g. ubuntu-latest). If you don't use the default permission of the GITHUB_TOKEN, give the Job or Workflow at least the contents: write permission. The goal of this Action is to be "the Action for committing files for the 80% use case". Therefore, you might run into issues if your Workflow falls into the not supported 20% portion. If your Workflow can't push the commit to the repository because of authentication issues, please update your Workflow configuration. -
21
git-cal
github like contributions calendar on terminal
git-cal generates a terminal-friendly contribution calendar for your Git activity, echoing the familiar heatmap seen on hosting sites but rendered in plain text. It scans your repositories’ commit history and aggregates changes per day, then prints a compact grid that highlights streaks and quieter periods. The output works in standard shells, making it handy for dashboards, status emails, or a lightweight snapshot of productivity without opening a browser. Options typically let you choose time ranges, color intensity (where terminals support it), and which repositories to include. Because it reads local Git metadata, it respects your privacy and can include private work you don’t push to public remotes. For developers who like quick visual feedback in the CLI, git-cal turns raw commit timestamps into an at-a-glance activity portrait. -
22
git-delete-merged-branches
Command-line tool to delete merged Git branches
A convenient command-line tool helping you keep repositories clean. Supports deletion of both local and remote branches. Detects multiple forms of de-facto merges (rebase merges, squash merges (needs --effort=3), single or range cherry-picks… leveraging git cherry). Supports workflows with multiple release branches, e.g. only delete branches that have been merged to all of master, dev and staging. Quick interactive configuration. Provider agnostic: Works with GitHub, GitLab, Gitea and any other Git hosting. Takes safety seriously. Deletion is a sharp knife that requires care. While git reflog would have your back in most cases, git-delete-merged-branches takes safety seriously. git push is used with --force-with-lease so if the server and you have a different understanding of that branch, it is not deleted. There is no use of os.system or shell code to go wrong. -
23
git-imerge
Incremental merge for git
Perform a merge between two branches incrementally. If conflicts are encountered, figure out exactly which pairs of commits conflict, and present the user with one pairwise conflict at a time for resolution. Reduce the pain of resolving merge conflicts to its unavoidable minimum, by finding and presenting the smallest possible conflicts: those between the changes introduced by one commit from each branch. Allow a merge to be saved, tested, interrupted, published, and collaborated on while it is in progress. Multiple incremental merges can be in progress at the same time. Each incremental merge has a name, and its progress is recorded in the Git repository as references under refs/imerge/NAME. The current state of an incremental merge can be visualized using the diagram command. An incremental merge can be interrupted and resumed arbitrarily, or even pushed to a server to allow somebody else to work on it. -
24
git-notify
Communicate important updates to your team via git commit messages
Communicate important updates to your team via git commit messages. Sometimes you need to communicate changes to other developers on your project. In a small team, a Slack message works okay, but in larger teams and distributed organizations (such as open-source projects), reaching everyone can be a pain. git-notify allows you to embed announcements into your git commit messages. And display them to another developer on a machine, far far away. Just add "git-notify:" to your git commit message, and anything that follows will be displayed when another developer pulls that commit, or switches from a branch that does not contain that commit to one that does. If you're using a merge or squash commit strategy on GitHub, you can also add them to the extended commit message when landing a PR. git-notify will display a message for every "git-notify:" prefix it finds in the commit log that was just pulled/merged/rebased/checked out. -
25
git-open
Type `git open` to open the GitHub page or website for a repository
Type git open to open the repo website (GitHub, GitLab, Bitbucket) in your browser. git open works with these hosted repo providers, git open --issue currently only works with GitHub, Visual Studio Team Services and Team Foundation Server. The preferred way of installation is to simply add the git-open script somewhere into your path (e.g. add the directory to your PATH environment or copy git-open into an existing included path like /usr/local/bin). Antigen will handle cloning the plugin for you automatically the next time you start zsh, and periodically checking for updates to the git repository. You can also add the plugin to a running zsh with antigen bundle paulirish/git-open for testing before adding it to your .zshrc. Add zgen load paulirish/git-open to your .zshrc file in the same function you're doing your other zgen load calls in. ZGen will take care of cloning the repository the next time you run zgen save, and will also periodically check for updates to the git repository.