Search Results for "tiny-workflow"

An open source Git extension for versioning large files. 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. Download and install the Git command line extension. Once downloaded and installed, set up Git LFS for your user account. In each Git repository where you want to use Git LFS, select the file types you'd like Git...

Git Town adds Git commands that make software development more efficient by keeping Git branches better in sync with each other. This reduces merge conflicts and the number of Git commands you need to run. Git is a flexible source code management system. The Git CLI (correctly) supports all possible ways of using Git equally well. It provides basic commands out of which Git users can implement their particular Git workflows. This generic design can make using the Git CLI repetitive in real...

git-bug is fully embedded in git, you only need your git repository to have a bug tracker. git-bug is distributed. Use your normal git remote to collaborate, push and pull your bugs! git-bug works offline, in a plane or under the sea? Keep reading and writing bugs! It prevents vendor lock-in: your usual service is down or went bad? You already have a full backup. It is fast, listing bugs or opening them is a matter of milliseconds. git-bug doesn't pollute your project, no files are added in...

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...

Captain - Convert your Git workflow to Docker containers ready for Continuous Delivery. Define your workflow in the captain.yaml and use captain to your Continuous Delivery service to create containers for each commit, test them and push them to your registry only when tests passes. Use captain build to build your Dockerfile(s) of your repository. If your repository has local changes the containers will only be tagged as latest, otherwise the containers will be tagged as latest, COMMIT_ID...