[Azure Devops] Auto complete support

[Berreek]

✨ What kind of change does this PR introduce? (Bug fix, feature, docs update...)

Feature.

⤵️ What is the current behavior?

Cannot mark PR as autocompleted.

🆕 What is the new behavior (if this is a feature change)?

Can mark PR as autocompleted by using new configuration parameter (setautocomplete) in repo command.

💥 Does this PR introduce a breaking change?

No, parameter is optional and set to false on default.

🐛 Recommendations for testing

N/A

📝 Links to relevant issues/docs

#938

🤔 Checklist before submitting

• All projects build
• Relevant documentation was updated

[jozefchmelar]

Thank you for your code @Berreek ! I used it in my fork and it works perfectly.

[Berreek]

@skolima Any update for it?

[skolima]

Could you update from master so that this branch builds, please? I'm also not sold on the naming - it's specific to Azure, while adding a general option. Azure calls this "set auto-complete" flag https://docs.microsoft.com/en-us/azure/devops/repos/git/pull-requests?view=azure-devops while GitHub (and Dependabot) call this auto-merging ( dependabot/feedback#954 ) and that's naming I'm more familiar with.

What would you say about naming the option setautomergeflag? (docs updated accordingly once we settle on a name).

@AnthonySteele could you perhaps comment?

[Berreek]

I updated the branch.

Regarding the name - I called it auto-complete beacuse I looked only on Azure to be honest. I agree with you that auto-merge will get better understanding since complete is Azure specific as you said.

Let me know if we stick with it.

[Berreek]

@skolima I renamed the option from setautocomplete to setautomerge - is there something else that need to be done in order to merge that PR?

[ykysel]

@Berreek @skolima could we get this merged? It will be very helpful

[skolima]

Truth be told, I don't think any of the original developers uses NuKeeper any more. But I'll try to find time to release this.