Search Results for "mark"

...Branches are shown using a graph which highlights commits that are included in the current revision. Explore the history of single files. Renamed and moved files are matched and shown in a single history. You do not need to mark files as renamed/moved. The system detects renamed files automatically. Find the last person that edited a specific part of a file. Double click on the line shows the commit and allows you to drill-down to other files. Version 2.x of Git Extensions runs on multiple platforms using Mono. The active community of Git Extensions is supporting Git Extensions since 2008.

git-flow-next is a branching model and a set of command-line extensions tailored to enforce that branching model for Git repositories. The underlying workflow was first described in 2010 and is designed around two long-lived branches (master (or main) for production-ready code, and develop for integration) and multiple supporting short-lived branches (feature, release, hotfix) for day-to-day development. With git-flow, each type of branch has explicit purpose and merge rules: features merge...

...It is possible to provide a list of commands to be executed in a folder after it is initialized as Git repository. Set path patterns to exclude from this extension. You can use wildcard and interrogation mark for respectively everything or any single character in the pattern.