Adrian Edwards

Closing this PR because it does not solve the underlying issue (fixing the duplicate key violation) - it only covers it up by hiding the error.

My $0.02: could we make the new option more descriptive? Like "facade_process_commit_messages"? Other users may not know what this is intuitively and the config is going to be most peoples...

i havent noticed this but this sounds like a perfect explaination for some of my observations that processing certain parts of collection that start out reallly fast and slow down...

https://github.com/chaoss/augur/blob/dabf0981834b77543d658204123bc9c9840b88ca/augur/tasks/git/dependency_tasks/dependency_util/dependency_calculator.py#L1-L28

Also, you dont need to re-create PRs to update them, pushing to, or even force-pushing to the branch that you created the PR with will automatically update it

as noted in #3414, i think the duplicate publishing was intentionally a feature because probabiltically weihted key use was something that was used previously but isnt anymore. if we want...

Based on the title, your existing, closed PR for this may update docs and a typo, so let's maybe merge those two pieces since they exist already (i assume). Then...

Closing as there are multiple parallel solutions and the one proposed in https://github.com/chaoss/augur/pull/3370 is more robust and complete in my opinion