Netlify-cms: Reimplement all-contributors using bot

[tech4him1]

Is your feature request related to a problem? Please describe.
https://github.com/all-contributors/all-contributors-bot/issues/5

Describe the solution you'd like

Describe alternatives you've considered

Additional context

[jakebolam]

A quick install and it will work with the existing .all-contributorsrc file.

See docs: https://all-contributors.js.org/docs/bot/installation

[tech4him1]

@erquhart @talves @verythorough Any reason to hold off on this?

[tech4him1]

@jakebolam Is there currently any way to just have the bot write to the file directly without making a separate PR? I'm not seeing anything in the docs, but maybe it's possible?

[erquhart]

@tech4him1 I assumed the bot handled merge conflicts proactively (not sure why I made that assumption, it's nontrivial functionality). Adding contributors wasn't the part I was most concerned with automating - it was rebasing pull requests when they inevitably conflict with one another. I'd like to see that functionality before bringing this back personally.

There's discussion here: https://github.com/all-contributors/all-contributors-bot/issues/62

_{Sent with GitHawk}

[tech4him1]

@erquhart Right, I agree with you on that. What if the bot just pushed, without creating a PR?

[erquhart]

Oh just saw your comment about directly committing, that might be an even better option!

_{Sent with GitHawk}

[verythorough]

This would be so great!

I like the idea of committing directly to avoid PR merge conflicts.

[jakebolam]

We recognize there is a gap here. We're totally planning to address this and have netlify and many others benefit from this.

Some UX we've seen is users regularly tag the wrong user, typos/auto complete. This same problem affects mentioned contributions.

Before we proceed on either option we will get an RFC going. (I think it would be difficult to support both right now).

Some discussion has started here and on https://github.com/all-contributors/all-contributors-bot/issues/62

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.