Search Results for "mathjax-master"

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

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

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

... for yadm. Support for detached working trees. If you are running a development version of Neovim (aka master), then breakage may occur if your build is behind latest. Gitsigns provides an on_attach callback which can be used to setup buffer mappings. This plugin is actively developed and by one of the most well regarded vim plugin developers. Gitsigns will only implement features of this plugin if: it is simple, or, the technologies leveraged by Gitsigns (LuaJIT, Libuv, Neovim's API, etc).

Reflow automatically creates pull requests, ensures the code review is approved, and squash merges finished branches to master with a great commit message template. Enforce code reviews across your team. Know that your entire team delivers code the same way. Reduce the knowledge needed to deliver great code. Have a commit history that's clean and actually usable. Revert features with ease (if needed). Work with diverse teams with less worry about different processes. Stop searching for other...

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

... is master but some projects choose to have develop or trunk or another branch for day-to-day development activities. We refer to this main development branch as the main development branch throughout this document to keep the text general. However in the command examples and ASCII-diagrams, we use master as an example of the main development branch.

Gitslave is a script for coordinated version control of large projects combining code from multiple independent repositories using Git. More flexible than traditional git submodules, gitslave provides a simple wrapper around command-line git that manages a directory tree with multiple subsidiary ("slave") git repositories in sub-directories of a "master" git repository. Any git command run from the "gits" wrapper will be performed in all the git repositories; for example gits checkout -b...

Python script to mirror a git repository with subversion It uses a basic common working directory, where git checkout the file for each commit of the master branch and then it will add, del, commit with a svn client.