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
With an eye to reusability, here's a design for a new badge. This came up for our own use at #1605 (comment), though a lot of folks use branches for their deploy pipelines, so I feel like it could be handy beyond Shields.
A future enhancement could allow overriding the message. Though that suggestion has come up before on other badges, and it might be a good problem to solve in a more global way.
The text was updated successfully, but these errors were encountered:
This badge format would be useful when you have commit id. It's not a problem for a bot or when you know where to find id ;-) I was thinking about a simpler API, where we know branch name and PR id. It would take one extra API call to get commit id from PR.
But since we are going to automatically put a badge with deploy info in PR you proposal would do the job!
Love the idea of showing the merge status of a PR! Perhaps I wrongly inferred it would be difficult to get the commit ID from an API call. Maybe then, the default label should be merge status.
With an eye to reusability, here's a design for a new badge. This came up for our own use at #1605 (comment), though a lot of folks use branches for their deploy pipelines, so I feel like it could be handy beyond Shields.
https://img.shields.io/github/commit-status/gh-pages/ed419b0a77d89094e11466797dfae68d92a2fab9
https://img.shields.io/github/commit-status/gh-pages/ed419b0a77d89094e11466797dfae68d92a2fab9?label=deploy%20status
A future enhancement could allow overriding the message. Though that suggestion has come up before on other badges, and it might be a good problem to solve in a more global way.
The text was updated successfully, but these errors were encountered: