-
Notifications
You must be signed in to change notification settings - Fork 113
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Build badges #399
Comments
It would be helpful if we could have this feature! |
Any update? |
I'd like to know that too |
Would love to have this feature |
would be nice to have this |
That would be useful |
Nothing yet? : ( i've got used to netlify badge and now I'm using amplifgy... miss so much a deploy status badge |
Would definitely find these useful, especially for the usecase of using amplify to host SSG rendered websites like gatsby. Netlify provides nice build badges that can be exposed through a variety of locations that give indication of build/deploy status and whether successful or not. Right now with amplify, you can code a button to perform a build via the webhook, but the badge would provide useful insight into that without having to go to the console or refresh website. |
please guys jaja it would be useful >:c |
Bump |
1 similar comment
Bump |
any news ? |
Any update to this? |
nothing yet guys :( |
Come on it's 2023 and still no build badges?? :( |
This would be a really nice feature |
This has taken 3 years of request any update |
Still awaiting a news |
Would love to see this feature! |
I hardly believe AWS will ever spend any time to work on this. I'm happy we moved away from Amplify towards more flexible CI/CD systems. |
bump |
Does anyone have a workaround for this? |
My workaround was Netlify |
Are there any updates on the badges for Amplify builds? |
Is your feature request related to a problem? Please describe.
CodeBuild provides build badges, however Amplify CI does not seem to expose them.
Describe the solution you'd like
Would be great to get build badges for repo READMEs
The text was updated successfully, but these errors were encountered: