GitReleaseNotes
GitReleaseNotes copied to clipboard
GitTools
Easily generate release notes
GitLab issue tracker is currently not supported and could be easily integrated once https://gitlab.com/gitlab-org/gitlab-ce/issues/30822 implemented. For now, it may be possible to do manually the filter on client side based...
As per headline. Usually it's the last issue closed from the previous release.
I guess the commit link is not very helpful. For instance, if a release only includes 1 commit (compared to the last release), it tries to compare that single commit...
When I try to run this command from within my repo, I get the following error: ``` Unhandled Exception: System.InvalidOperationException: Number of ordinal arguments must at least {0}. at Args.ModelBindingDefinition`1.EnsureCorrectNumberOfOrdinalArguments(IEnumerable`1...
Setting the `developmentDependency` flag in the `Nuspec` might be a good idea, as it means that if people add GitReleaseNotes as a NuGet package to their project, when they then...
``` Unhandled Exception: System.InvalidOperationException: Number of ordinal arguments must at least {0}. at Args.ModelBindingDefinition`1.EnsureCorrectNumberOfOrdinalArguments(IEnumerable`1 ordinalArgs) at Args.ModelBindingDefinition`1.BindModel(TModel model, IEnumerable`1 args) at Args.ModelBindingDefinition`1.CreateAndBind(IEnumerable`1 args) at GitReleaseNotes.Program.Main(String[] args) in C:\projects\gitreleasenotes\src\GitReleaseNotes\Program.cs:line 32 ```
Now GitTools.IssueTrackers supports JIRA, we can improve GitReleaseNotes to support it as well (should be out of the box, but doing some testing and minor improvements).
Unfortunately, this causes GitReleaseNotes to dump all closed issues from all projects. Not sure if other issue trackers are supported, only tested with Jira.
I am running: ``` powershell GitReleaseNotes.exe . /OutputFile ReleaseNotes.md /AllTags /Verbose ``` I have 3 remotes: ``` powershell C:\proj\code-cracker> git remote -v code-cracker https://github.com/code-cracker/code-cracker.git (fetch) code-cracker https://github.com/code-cracker/code-cracker.git (push) origin https://github.com/giggio/code-cracker.git...
We should be able to use only Issues, and not Pull Requests when generating a release note. In my case, the PRs are redundant, I don't need them there.