Hi@carabasdaniel !

Thanks for this PR.

Can you please also provide test cases?

Hi@ferrarimarco, I've added two unit tests and amended the commit.

Any update

I met similar error

/usr/local/bundle/gems/octokit-4.14.0/lib/octokit/response/raise_error.rb:16:in `on_complete': GET https://api.github.com/repos/volcano-sh/volcano/compare/d454490cca88891c1ca8b1a85c4506d115574a21...v0.1: 404 - No common ancestor between d454490cca88891c1ca8b1a85c4506d115574a21 and v0.1. // See: https://developer.github.com/v3/repos/commits/#compare-two-commits (Octokit::NotFound)

@ferrarimarco any update on this PR?

Hi. I'm thinking about the best strategy here. While this PR let you have a changelog, it may be an issue it silently fails during a CI build where you automatically generate the changelog.

Thanks, @carabasdanie.
The points of@ferrarimarco are valid.

In order to not change standard behavior we can implement this behavior with a special flag, like--continue-with-errors

Hi@ferrarimarco@skywinder,

Added an option for continue_with_errors and rebased to latest master. Extracted add tag to pull request for rubocop complexity in generator fetcher.

(This code will have some movement under it, as we're waiting on#784 to land, which makes changes in the same places.)

@carabasdaniel can you rebase against the latest master?

Hi@ferrarimarco,

Rebased but had to remove the initially added unit tests as they were no longer valid.

Have the same problem as@hzxuzhonghu would love to see this PR merged!

Same problem here...any updates about this PR?

👍

This will be so helpful. Since the tool breaks because of a parent-less commit.

We've also hit this issue. Any updates about when this can be merged? Thanks :)

The blocker is an unmet note above:

thecontinue_with_errors setting is mostly "read" at the beginning, then no more is done with it.

And, I can not find any test code which does things with this new setting.