Jake Ginnivan

When issue tracker is not found, remote should be used

2

This feature no longer works. If using Github for source and issues it used to use the remote defined in the repo to infer the issue tracker. Also worked for...

The `Commits: sha...sha` should link to /compare/sha...sha on github.

It should raise an error, I don't think there would be a migration path

We need to encode characters which do not render in markdown properly

We should try and support as many date formats as we can, and if we fail simple append the unparsed date to the title

Add tags to be excluded option

3

something like `/excludeTags wontfix` or something like this to easily filter out issues which are not fixed.

Sometimes issue numbers are put in branch names instead of in the commit messages. This should be supported

Command line args for a specific iissue provider should not be visible unless /issueTracker is specified

1

Or they should be grouped down the bottom

update nuspec with release notes

10

So I can just hit publish