It seems since github-changelog-generator v1.15.0 dropped last year that the generator has lost the ability to determine the user and project from the current repo its run in.
Now when we run it we have to call the gem directly and pass these in as arguments to get it to work.
So this change resolves the issue, and means we can go back to using bundle exec rake changelog.
It seems since github-changelog-generator v1.15.0 dropped last year that the generator has lost the ability to determine the
user
andproject
from the current repo its run in.Now when we run it we have to call the gem directly and pass these in as arguments to get it to work.
So this change resolves the issue, and means we can go back to using
bundle exec rake changelog
.