Search Results for "tool all in one"

GitHub Actions Version Updater is GitHub Action that is used to update other GitHub Actions in a Repository and create a pull request with the updates. It is an automated dependency updater similar to GitHub's Dependabot, but for GitHub Actions. GitHub Actions Version Updater first goes through all the workflows in a repository and checks for updates for each of the action used in those workflows. If an update is found and if that action is not ignored then the workflows are updated with the latest release of the action being used. If at least one workflow file is updated then a new branch is created with the changes and pushed to GitHub. ...

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.

...Checkout out this demo project, which was set up using PyScaffold and if you are still not convinced yet, also have a look at these reasons to use PyScaffold. After cd-ing into your new project and creating (or activating) an isolated development environment (with virtualenv, conda or your preferred tool), you can do the usual editable install. All configuration can be done in setup.cfg like changing the description, URL, classifiers, installation requirements and so on as defined by setuptools. That means in most cases it is not necessary to tamper with setup.py.

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

Tracking a Xcode project in a version control system is annoying. Simply adding files can lead to merge conflicts that have to be solved manually, although it would be possible to resolve the conflict automatically if the merge algorithm would be aware of the structure of Xcode's project file. After long and annoying merge sessions in one of my projects, I came to the conclusion, that writing a merge driver for git which understands the structure of the project file would be a worthwhile...

...Can display a statistical timeline analysis. Scans for all filetypes (by extension) found in the repository. Multi-threaded; uses multiple instances of git to speed up analysis when possible.

Pynta is flexible web framework written in Python. All development going on https://github.com/lig/pynta

A tool to keep database objects and stored procedures synchronized with application code in a multi-developer environment with a short release cycle and multiple development branches. Tie-in to svn (subversion) for version control.

KappaSVN is a tool of management SVN through a file manager Nautilus. It is used to handle all kinds of subversion operations graphically.

TMerge is a subversion code merge tool designed for working with ticket system. It can be used by developer, QA person to move code from one branch to another based on the ticket number in the commit message.

VersionWeb is a tool for web pages version control in web itself. VersionWeb allows the authors to do checkout a file, commit, add, remove, rename, etc, that is, the operations more common in version control. The authors can control the versions of your p