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
Add checks, or "statuses" as they're called in the Azure DevOps API. This implicitly makes a pull request not mergeable until the status is "succeeded"
We want to add this throughout the provider repos. So it would behoove us to figure out a way to do this in a generic manner.
Old thought was to use rabbitmq events, but that's no longer an obvious solution as it does in fact induce a lot of overhead for users trying to install Wharf. Would be better to just let the API talk with the providers directly.
Add checks, or "statuses" as they're called in the Azure DevOps API. This implicitly makes a pull request not mergeable until the status is "succeeded"
API docs: https://docs.microsoft.com/en-us/rest/api/azure/devops/git/statuses/create?view=azure-devops-server-rest-5.0
On the commit:
![image](https://user-images.githubusercontent.com/2477952/119137401-100f2280-ba41-11eb-853c-ef822abe92f2.png)
In commit list:
![image](https://user-images.githubusercontent.com/2477952/119137409-12717c80-ba41-11eb-8bf2-4d4072cf67c2.png)
We want to add this throughout the provider repos. So it would behoove us to figure out a way to do this in a generic manner.
Old thought was to use rabbitmq events, but that's no longer an obvious solution as it does in fact induce a lot of overhead for users trying to install Wharf. Would be better to just let the API talk with the providers directly.
Suggest writing an RFC on this: https://github.com/iver-wharf/rfcs
The text was updated successfully, but these errors were encountered: