Search Results for "act"

Tig is an ncurses-based text-mode interface for git. It functions mainly as a Git repository browser, but can also assist in staging changes for commit at chunk level and act as a pager for output from various Git commands. Tig allows you to browse changes in a Git repository and can additionally act as a pager for output of various Git commands. When used as a pager, it will display input from stdin and colorize it. When browsing repositories, Tig uses the underlying Git commands to present the user with various views, such as summarized commit log and showing the commit with the log message, diffstat, and the diff. ...

...Bundle-based cloning and Git LFS are included for handling repositories and large files efficiently. Users also get a repository browsing interface, JSON API, SDK, webhooks, and configurable push policies. Server instances act as disposable caches, allowing multiple machines to serve the same repositories without a database, leader, or shared local filesystem.

git-remote-dropbox is a Git remote helper that lets Dropbox act like a real Git remote. It provides a transparent bridge between Git and a Dropbox folder or shared Dropbox folder. After installation and login, users can clone from or push to remote URLs that use the dropbox scheme. The helper preserves traditional Git remote guarantees, including atomic behavior even when multiple people operate on the repository.

This library defines an object oriented representation of the GitHub API. By "object oriented" we mean there are classes that correspond to the domain model of GitHub (such as GHUser and GHRepository), operations that act on them as defined as methods (such as GHUser.follow()), and those object references are used in favor of using string handle (such as GHUser.isMemberOf(GHOrganization) instead of GHUser.isMemberOf(String)) The library supports both github.com and GitHub Enterprise. Most of the GitHub APIs are covered, although there are some corners that are still not yet implemented. ...

Combine the advantages of a monorepo with those of multirepo setups by leveraging a blazingly-fast, incremental, and reversible implementation of git history filtering. The partial repo will act as a normal git repository but only contain the files found in the subdirectory and only commits affecting those files. The partial repo supports both fetch as well as push operation. This helps not just to improve performance on the client due to having fewer files in the tree, it also enables collaboration on parts of the monorepo with other parties utilizing git's normal distributed development features. ...