Open Source JavaScript Git Software
Sort By:
JavaScript Git Software
View 80 business solutionsBrowse free open source JavaScript Git Software and projects below. Use the toggles on the left to filter open source JavaScript Git Software by OS, license, language, programming language, and project status.
-
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.
-
Custom VMs From 1 to 96 vCPUs With 99.95% UptimeLive migration and automatic failover keep workloads online through maintenance. One free e2-micro VM every month.
-
1
ungit
A tool to simplify the use of git, on any platform, anywhere
Git is known for being a versatile distributed source control system that is a staple of many individuals, communities, and even for the City of Chattanooga to crowd source bicycle parking locations. However, it is not known for userfriendliness or easy learning curve. Ungit brings user friendliness to git without sacrificing the versatility of git. Git and github both supports PGP signing. Within Ungit these features can be enabled. Currently, Ungit DOES NOT support GPG authentication! While git allows robust programmatic authentication via credential-helper, I could not find an easy way to do something equivalent with GPG. Therefore, password-less gpg authentication or 3rd party gpg password must be configured when using Ungit to commit with gpg. Ungit will watch git directory recursively upon page view and automatically refresh contents on git operations or changes on files that are not configured to be ignored in .gitignore. -
2
Husky
Git hooks made easy
Husky is a tool that makes handling Git hooks a lot easier, and lets you run the scripts you want at those stages. It works by including an object right within your package.json file. This then configures Husky so that it runs the scripts you specify. After that, it's Husky's responsibility to manage at which point in the Git lifecycle your scripts will run. Husky helps to improve your commits, lets you run tests, lint code and more when you commit or push. It is very lightweight, with zero dependencies and is capable of supporting all Git hooks. -
3
isomorphic-git
A pure JavaScript implementation of git for node and browsers!
A pure JavaScript implementation of git for node and browsers! Clone repos, create commits, push branches and more in client-side JS. It uses the same on-disk format as git so it works with existing repos. isomorphic-git is a pure JavaScript implementation of git that works in node and browser environments (including WebWorkers and ServiceWorkers). This means it can be used to read and write to git repositories, as well as fetch from and push to git remotes like GitHub. isomorphic-git aims for 100% interoperability with the canonical git implementation. This means it does all its operations by modifying files in a ".git" directory just like the git you are used to. The included isogit CLI can operate on git repositories on your desktop or server. isomorphic-git aims to be a complete solution with no assembly required. The API has been designed with modern tools like Rollup and Webpack in mind. -
4
NodeGit
Native Node bindings to Git
Asynchronous native Node bindings to libgit2. NodeGit will work on most systems out-of-the-box without any native dependencies. If you receive errors about libstdc++, which are commonly experienced when building on Travis-CI, you can fix this by upgrading to the latest libstdc++-4.9. If you wish to help contribute to NodeGit it is useful to build locally. If you encounter errors, you most likely have not configured the dependencies correctly. You will need libpcre, libpcreposix, libkrb5, libk5crypto, and libcom_err libraries installed on your Linux machine. When building locally, you will also need development packages for kerberos and pcre, so both pcre-config, and krb5-config utilities must be present on your machine. -
Train ML Models With SQL You Already KnowBuild and deploy ML models using familiar SQL. Automate data prep with built-in Gemini. Query 1 TB and store 10 GB free monthly.
-
5
Netlify CMS
A Git-based CMS for static site generators
Open source content management for your Git workflow. Use Netlify CMS with any static site generator for a faster and more flexible web project. Get the speed, security, and scalability of a static site, while still providing a convenient editing interface for content. Content is stored in your Git repository alongside your code for easier versioning, multi-channel publishing, and the option to handle content updates directly in Git. Netlify CMS is built as a single-page React app. Create custom-styled previews, UI widgets, and editor plugins or add backends to support different Git platform APIs. Getting started is simple and free. Choose a template that’s pre-configured with a static site generator and deploys to a global CDN in one click. You get to implement modern front end tools to deliver a faster, safer, and more scalable site. Editors get a friendly UI and intuitive workflow that meets their content management requirements. -
6
Commitizen for contributors
The commitizen command line utility
When you commit with Commitizen, you'll be prompted to fill out any required commit fields at commit time. No more waiting until later for a git commit hook to run and reject your commit (though that can still be helpful). No more digging through CONTRIBUTING.md to find what the preferred format is. Get instant feedback on your commit message formatting and be prompted for required fields. Commitizen is currently tested against Node.js 12, 14, & 16, although it may work in older versions of Node.js. You should also have npm 6 or greater. When you're working in a Commitizen-friendly repository, you'll be prompted to fill in any required fields, and your commit messages will be formatted according to the standards defined by project maintainers. Installing and running Commitizen locally allows you to make sure that developers are running the exact same version of Commitizen on every machine. -
7
git-sketch-plugin
A Git client generating pretty diffs built right into Sketch
A Git client generating pretty diffs built right into Sketch. A Git client built right into Sketch. The plugin really improves the review process by exporting an image for every part of the design. Every member of the team can quickly see what the next iteration will change through Github’s interface. Each step of the design process is now documented. Newcomers are able to understand how we ended up with the current iteration and why we went with some options and not others. Create a new branch when you start working on a new feature. Work normally on your design. Save the file. Commit the changes with a meaningful message describing them. The plugin will extract the artboards in your file in order to show the differences easily. Push your changes to the remote. Create a pull request from your branch to the master branch. Voila. Your co-workers can review the changes, comment on them and approve them. Once approved, merge the pull request. -
8
pretty-quick
Get Pretty Quick
Runs Prettier on your changed files. Pre-commit mode. Under this flag only staged files will be formatted, and they will be re-staged after formatting. Partially staged files will not be re-staged after formatting and pretty-quick will exit with a non-zero exit code. The intent is to abort the git commit and allow the user to amend their selective staging to include formatting fixes. When not in staged pre-commit mode, use this flag to compare changes with the specified branch. Defaults to master (git) / default (hg) branch. Do not resolve prettier config when determining which files to format, just use standard set of supported file types & extensions prettier supports. This may be useful if you do not need any customization and see performance issues. Check that files are correctly formatted, but don't format them. This is useful on CI to verify that all changed files in the current branch were correctly formatted. -
9
simple-git-hooks
A simple git hooks manager for small projects
A simple git hooks manager for small projects. A git hook is a command or script that is going to be run every time you perform a git action, like git commit or git push. If the execution of a git hook fails, then the git action aborts. For example, if you want to run linter on every commit to ensure code quality in your project, then you can create a pre-commit hook that would call npx lint-staged. Check out lint-staged. It works really well with simple-git-hooks. You can look up about git hooks on the Pro Git book. simple-git-hooks works well for small-sized projects when you need quickly set up hooks and forget about it. However, this package requires you to manually apply the changes to git hooks. If you update them often, this is probably not the best choice. Also, this package allows you to set only one command per git hook. -
Ship Agents FasterGemini Enterprise Agent Platform lets you rapidly build, scale, govern and optimize production-ready agents grounded in your organization's data. The platform enables developers to build custom or pre-built agents for virtually any use case. New customers get $300 in free credits.
-
10
All Node.js versions
List all available Node.js versions
List all available Node.js versions. Sorted from the most to the least recent. Includes major release and LTS information. This package is an ES module and must be loaded using an import or import() statement, not require(). The return value resolves to an object with the following properties. List of available Node.js versions and related information. Sorted from the most to the least recent Node.js version. List of Node.js major releases sorted from the most to the least recent. -
11
lint-staged
Run linters on git staged files
Run linters against staged git files and don't let anything slip into your code base! Linting makes more sense when run before committing your code. By doing so you can ensure no errors go into the repository and enforce code style. But running a lint process on a whole project is slow, and linting results can be irrelevant. Ultimately you only want to lint files that will be committed. This project contains a script that will run arbitrary shell tasks with a list of staged files as an argument, filtered by a specified glob pattern. Linter commands work on a subset of all staged files, defined by a glob pattern. lint-staged uses micromatch for matching files. The concept of lint-staged is to run configured linter tasks (or other tasks) on files that are staged in git. lint-staged will always pass a list of all staged files to the task, and ignoring any files should be configured in the task itself. -
12
Conventional Changelog
Generate changelogs and release notes from a project's commit messages
The conventional-changelog repo is managed as a monorepo; it's composed of many npm packages. It's recommended you use the high-level standard-version library, which is a drop-in replacement for npm's version command, handling automated version bumping, tagging, and CHANGELOG generation. Alternatively, if you'd like to move towards completely automating your release process as an output from CI/CD, consider using semantic-release. We specifically limit our support to LTS versions of Node, not because this package won't work on other versions, but because we have a limited amount of time, and supporting LTS offers the greatest return on that investment. It's possible this package will work correctly on newer versions of Node. It may even be possible to use this package on older versions of Node, though that's more unlikely as we'll make every effort to take advantage of features available in the oldest LTS version we support. -
13
ForkHub
GitHub client for Android based on the abandoned app
ForkHub started off as a fork of the Android app from GitHub, and has since seen lots of improvements. You can see a comprehensive list of changes in the change log. ForkHub is an open source GitHub client that started as a fork of the GitHub Android app after they abandoned it, and has seen a lot of improvements since then. Stay up-to-date with all your GitHub activity thanks to notifications and an integrated news feed for organizations, friends, and repositories. Create, manage, and discuss topics on any GitHub repository or view the dashboard topics to keep in touch with all the issues we've reported, assigned, or participate in discussion on. You can also view and filter a repository's edition list and bookmark it for quick access. See your GitHub organizations' repositories, members and teams and stay up to date with all the events. Discover, share, and discuss code snippets using the integrated GitHub Gists support. -
14
Git History
Quickly browse the history of a file from any git repository
Git History is a web-based tool for visually browsing the history of a file from a Git repository. It lets users inspect how a file changed over time by replacing a supported repository URL with the Git History domain. The tool works with GitHub, GitLab, and Bitbucket file URLs, making it useful across several common code-hosting platforms. It presents changes as an animated, readable timeline instead of requiring users to manually step through commits. The project also offers browser extensions, a bookmarklet, a CLI, and a VS Code extension for different workflows. Git History is especially useful for developers who want to understand the evolution of code, documentation, or configuration files quickly. -
15
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! -
16
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. -
17
git-cz
Semantic Git commits
git-cz is a command-line tool designed to guide developers in writing structured, conventional commits. Rather than manually typing commit messages, this tool prompts you to select commit types, scopes, and write descriptions according to a defined format. It integrates with the popular commitizen ecosystem so that when you run npx git-cz or similar, you are prompted through a workflow instead of free-form message. The project emphasises consistency and readability in commit history, helping teams enforce semantic or conventional commit message formats. It supports custom configuration (for example via a changelog.config.js file) so you can adapt the prompts or types to your project’s conventions. Because it is open source (licensed under Unlicense) it can be freely integrated within CI pipelines or commit hooks to standardise message formats. -
18
git-peek
git repo to local editor instantly
git peek is the fastest way to open a remote git repository in your local text editor. Use it when you want to browse or search other people's code with your own editor. Pass git peek a git repository or a github link, and it will quickly fetch and open it in your local editor. It stores the repository in a temporary directory and deletes it when you close the editor or git peek. If you don't pass git peek input, it will let you search Github repositories and show trending repositories. If you paste a link to a file on GitHub, it will quickly open the file in your local editor. If you pass it a GitHub repository, it fetches a tarball instead of using git and decompresses it while downloading it (streaming). From unscientific benchmarks, this is about 2x faster than cloning. While downloading & decompressing the tarball, it also downloads the specific file linked to (or the README.md) via JSDelivr's CDN. -
19
Colección de páginas HTML5 con ejemplos y casos de uso del nuevo lenguaje de marcado así como de la combinación del mismo con estilos CSS de nivel 3, gráficos vectoriales SVG y script mediante ECMAScript 5.
-
20
meta
Tool for turning many repos into a meta repo
Tool for turning many repos into a meta repo. why choose many repos or a monolithic repo, when you can have both with a meta repo? meta is powered by plugins that wrap common commands, letting you execute them against some or all of the repos in your solution at once. meta is built on loop, and as such inherits loops ability to easily target a particular set of directories for executing a common command (eg meta git status --include-only dir1,dir2. See loop for more available options). meta is a tool for managing multi-project systems and libraries. It answers the conundrum of choosing between a mono repo or many repos by saying "both", with a meta repo! Give every engineer on your team the same project setup, regardless of where it's cloned. Execute arbitrary commands against many repos to manage your projects. Easily wrap commands for working with any platform, not just Node! -
21
np
A better `npm publish`
Ensures you are publishing from your release branch (main and master by default). Ensures the working directory is clean and that there are no unpulled changes. Reinstalls dependencies to ensure your project works with the latest dependency tree. Ensures your Node.js and npm versions are supported by the project and its dependencies. Bumps the version in package.json and npm-shrinkwrap.json (if present) and creates a git tag. Prevents accidental publishing of pre-release versions under the latest dist-tag. Publishes the new version to npm, optionally under a dist-tag. Rolls back the project to its previous state in case publishing fails. Pushes commits and tags (newly & previously created) to GitHub/GitLab. Enables two-factor authentication on new repositories. Opens a prefilled GitHub Releases draft after publish. See exactly what will be executed with preview mode, without pushing or publishing anything remotely.
- Previous
- You're on page 1
- Next
