search
Found 13 packages
GitVersion.Tool✓
Derives SemVer information from a repository following GitFlow or GitHubFlow. This is the .NET Core Global Tool allowing usage of GitVersion from command line.
v6.6.0
↙ 102.6M / total
GitVersioningGitVersionGitFlowVersionGitFlow
GitVersion.CommandLine✓
Derives SemVer information from a repository following GitFlow or GitHubFlow.
v5.12.0
↙ 7.5M / total
GitVersioningGitVersionGitFlowVersionGitFlow
GitVersion.MsBuild✓
Stamps an assembly with git information based on SemVer.
v6.6.0
↙ 7.0M / total
GitVersioningGitVersionGitFlowVersionGitFlow
GitInfo
Access commit information from MSBuild and C#/F#/VB code, and infer SemVer from branch, tag or version file in Git repository.
v3.6.0
↙ 10.4M / total
MSBuildGitVersioningGitVersionGitFlowVersion
GitVersionTask✓
Stamps an assembly with git information based on SemVer.
v5.5.1
↙ 3.8M / total
GitVersioningGitVersionGitFlowVersionGitFlow
GitVersion.Core✓
Derives SemVer information from a repository following GitFlow or GitHubFlow. This is the Core library which both GitVersion cli and Task use allowing programatic usage of GitVersion.
v6.6.0
↙ 248.7K / total
GitVersioningGitVersionGitFlowVersionGitFlow
git-flow-version
git-flow-version creates predictable and opinionated SemVer 2.0.0 version numbers for git flow repositories.
v0.17.0
↙ 46.6K / total
GitGitFlowVersioningSemVerContinuous
pkg
GitHubFlowVersion
The easy way to use semantic versioning (semver.org) with GitHub Flow
v1.3.2
↙ 33.3K / total
GitHubFlowVersioningSemVerSemanticVersioningContinuous
pkg
Ktos.Build.GitVersion
This nuget updates your AssemblyInfo.cs with data from git repository based on GitFlow model (http://nvie.com/posts/a-successful-git-branching-model/), allowing you to create Semantic Versioning (http://semver.org/). It is basically a modification of GitVersion (https://github.com/ParticularLabs/GitVersion). Main differences are that using MSBuildCommunityTasks the AssemblyInfo.template.cs file is being changed with some variables being changed to proper version info, instead of creating completely new AssemblyInfo.cs. Reasons are: * I don't like GitVersion full versioning (like 1.2.3+4.Branch.master.Sha.12345678901234567890), so I can use here my own versioning scheme (like 1.2.3+4.master.1234567) (without "branch", "sha" and with short SHA hash); * Automatically generated assemblies from GitVersion were not compatible with NETMF.
v1.1.0
↙ 17.3K / total
gitflowgitversiongitsemver
DashDashVersion
This libary can generate a version numbers for a git flow repository.
v0.17.0
↙ 39.6K / total
GitGitFlowVersioningSemVerContinuous
NoeticTools.Git2SemVer.MSBuild✓
Automated Semantic Versioning for Visual Studio and dotnet CLI.
v3.3.1
↙ 13.5K / total
VersioningSemverGitMSBuildGitFlow
NoeticTools.Git2SemVer.Framework✓
Framework to generate Semantic Versioning from Git repository and conventional commits. Used by other Git2SemVer projects.
v1.1.0
↙ 455 / total
VersioningSemverGitGitFlowGitFlowVersion
pkg
AutoCake.Release
This package contains a git-flow based release template. Starting from either the develop branch or an release-branch, this script will attempt to validate a release build. The script uses GitVersion to calculate the release version number and takes care of all the necessary branching and tagging during the build. Building happens via a Cake action, and normally simply calls out to the standard 'build.cake' file for the project. If successful, it will merge that release into the master-branch and rebuild the actual release to create the release artefacts. On success of that step, the release branch will be merged back into the develop branch to start the next development cycle. If the release fails, this script will undo all changes to master, but will leave the release branch open so that the release can be fixed. Subsequent release attempts will reuse the existing release branch, even if started from the develop branch.
v2.2.0
↙ 19.9K / total
CakeRelease