feat: implement requiredStatusChecks for GitHub and GitLab

[sarunint]

Closes #1853 (partially)

[rarkins]

There are some obvious use cases here but also some less obvious.

1. If all required status checks are present and all passing: succeeded
2. If any required status checks are present and failed: failed
3. If only some of the status checks are present but all that are present are passing: pending?

The key question is: what to do if the user configures a required status check that fails to show up? I think we should probably be pending forever. What do you think?

[sarunint]

Ha, I totally missed those cases.

[sarunint]

Let me think for a while.

Also, should I do this for other platforms in this PR? Or should I separate them up?

[rarkins]

Ideally we would implement this for all platforms that could support it. It's OK to note a feature is "platform X only" but it can confuse users even still, so ideally we don't do that.

[sarunint]

@rarkins I ended up implement for both GitHub and GitLab.

[rarkins]

@leipert could you glance at the GitLab part of this?

[viceice]

Can we extract some util function for this? I see a lot duplicated code.

[rarkins]

Should we be applying the same logic to check runs? What happens if the user applies requiredStatusChecks while also there are some check runs?

[sarunint]

I'll see what I can do.

[rarkins]

Check runs (github) support. Also, possible to de-duplicate the core logic between github and gitlab implementations?

[viceice]

@sarunint any news? Are you planning any changes?

[viceice]

This should be simple adaptable for bitbucket and bitbucket-server.

azure would be more difficult.

renovate/lib/platform/azure/index.ts

Line 353 in 4adb0c0

const branch = await azureApiGit.getBranch(

branch.commit.statuses

https://docs.microsoft.com/en-us/rest/api/azure/devops/git/statuses/list?view=azure-devops-rest-5.1
https://docs.microsoft.com/en-us/rest/api/azure/devops/git/pull%20request%20statuses/list?view=azure-devops-rest-5.1

[sarunint]

@viceice Sorry, I've been very busy this month. I'll try to fix things up this weekend.

[viceice]

aditional azure info

GitBranchStatus interface
https://github.com/microsoft/azure-devops-node-api/blob/d4b692556db58a418e5d7c2b01fb68978746b3b4/api/interfaces/GitInterfaces.ts#L736-L760

GitCommitRef interface
https://github.com/microsoft/azure-devops-node-api/blob/d4b692556db58a418e5d7c2b01fb68978746b3b4/api/interfaces/GitInterfaces.ts#L804-L864

GitStatus interface
https://github.com/microsoft/azure-devops-node-api/blob/d4b692556db58a418e5d7c2b01fb68978746b3b4/api/interfaces/GitInterfaces.ts#L2456-L2496

[viceice]

Needs deconflicting

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}