search

ljharb / repo-report

CLI to list all repos a user has access to, and report on their configuration in aggregate.
MIT License
24 stars 11 forks source link

add metric: "Require deployments to succeed before merging" #82

Open ljharb opened 2 years ago

ljharb commented 2 years ago

This checkbox is under branch protections:

Screen Shot 2022-04-05 at 10 44 09 AM
ljharb commented 2 years ago

https://github.blog/changelog/2022-04-12-required-deployments/

thehanimo commented 2 years ago

I see a requiresStatusChecks under BranchProtectionRule. Is that it?

ljharb commented 2 years ago

It's possible this isn't in the API yet; i'll inquire.

thehanimo commented 2 years ago

Oh yea nvm. "Require status checks to pass before merging" is a different metric.

luis-iaggbs commented 1 year ago

@ljharb do you know when we could have this metric included into the API rest? This is a great feature to insert in any workflow working with environments.

ljharb commented 1 year ago

@lmartinezviewnext the "on hold" label means it's not in github's api. as soon as Github adds it, we can add it here.

KamranBiglari commented 1 year ago

API is not available for this feature and it's not possible to select an environment if it's not deployed on that environment. environment list is only visible once it's deployed on that env for the first time.

ljharb commented 1 year ago

@KamranBiglari thanks for confirming. we could still require an environment name here, and to satisfy it, you'd have to successfully deploy it before requiring it, just like a branch protection.

ddaniels-andmore commented 1 year ago

This was also confusing for me as well. We are creating a step-by-step for setting up a brand new repository and would like to have this rule setup. The way it functions now requires us to create the repo, deploy it and then set the rule. Kind of backwards, no?