You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently the mergebot only has two statuses for statuses (ignoring that statuses can be different between PRs and stagings since 5c1caa1):
required, so the mergebot needs to receive the status every time for the PR to progress
ignored, so the mergebot doesn't care about the status
However over time we've seen a new need: sub-repo statuses, which are only triggered some time (e.g. based on files touched, team, etc...) but need to block the PR if and when they are failed.
This should be pretty easy to implement: in PullRequests._compute_statuses, the default value for a status state just needs to be provided by the StatusConfiguration object.
The text was updated successfully, but these errors were encountered:
If a status is defined as `optional`, then the PR is considered valid
if the status is never sent, but *if* the status is sent then it
becomes required.
Note that as ever this is a per-commit requirement, so it's mostly
useful for conditional statuses.
Fixes#1062
... by default. Optional statuses we haven't at least received a
`pending` for are irrelevant to the PR's state, so should remain
hidden.
This subtetly was missed when fixing #1062Fixes#1066
Currently the mergebot only has two statuses for statuses (ignoring that statuses can be different between PRs and stagings since 5c1caa1):
However over time we've seen a new need: sub-repo statuses, which are only triggered some time (e.g. based on files touched, team, etc...) but need to block the PR if and when they are failed.
This should be pretty easy to implement: in
PullRequests._compute_statuses
, the default value for a status state just needs to be provided by theStatusConfiguration
object.The text was updated successfully, but these errors were encountered: