Fixing AutoMerge issue with Azure DevOps

[tapaszto]

This PR is fixing the #1152 Azure DevOps related issue by getting the Azure DevOps user Id on the fly and putting it into azuredevops.GitPullRequest.AutoCompleteSetBy.

[codecov]

Codecov Report

Merging #1289 (709defa) into master (9e92a36) will decrease coverage by 0.04%.
The diff coverage is 54.54%.

@@            Coverage Diff             @@
##           master    #1289      +/-   ##
==========================================
- Coverage   70.05%   70.00%   -0.05%     
==========================================
  Files          74       74              
  Lines        5540     5545       +5     
==========================================
+ Hits         3881     3882       +1     
- Misses       1303     1305       +2     
- Partials      356      358       +2     

Impacted Files	Coverage Δ
server/server.go	62.40% <0.00%> (ø)
server/events/vcs/azuredevops_client.go	65.67% <60.00%> (-1.17%)	⬇️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 9e92a36...709defa. Read the comment docs.

[tapaszto]

Hi @lkysow

Can You advise please why the ci/circleci: test is pending? Do we need to do any further steps in order to get our PR merged?

[Dilergore]

Hi @lkysow ,

Could you please take a look? We would like to continue with other enhancements for Azure DevOps which for this is a prerequisite.

Thanks!

[acastle]

Hi @tapaszto, it seems your branch has drifted behind master a bit. If you could either merge or rebase to resolve the conflicts I will be happy to get this merged in.

[tapaszto]

Hi @acastle,

I performed a merge and resolved the conflicts, can You approve the PR please?

[acastle]

LGTM 🚀

[tapaszto]

Hi @acastle ,

Thanks for approving the PR, but I'm not sure what to do now, can You advise please? Will it be automatically merged or do I need to perform any further steps?

[acastle]

Hi @tapaszto, our typical process is to get two sets of eyes from the maintainer group on non trivial PRs before they are merged. Once another maintainer gives an ok we will get this merged and released.

There is nothing further you need to do at this point. I can't comment on when exactly you can expect these changes to be in a release but it will likely be after the holidays as a number of the maintainers are enjoying some well deserved time off 😀

[tapaszto]

Hi @lkysow & @acastle,

Can you advise who can be the second approver in order to get our PR merged?

[lkysow]

LGTM