-
-
Notifications
You must be signed in to change notification settings - Fork 110
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
Manual & remote (HTTP) deployments through GitHub UI/API #147
Manual & remote (HTTP) deployments through GitHub UI/API #147
Conversation
❌ Deployment FAILED |
❌ Deployment FAILED |
❌ Deployment FAILED |
❌ Deployment FAILED |
❌ Deployment FAILED |
❌ Deployment FAILED |
✅ Deployment SUCCESS |
✅ E2E tests SUCCESS |
✅ Deployment SUCCESS |
✅ E2E tests SUCCESS |
✅ Deployment SUCCESS |
@Demmonius I believe I've fixed/understood everything that wasn't clear. Could you update the production workflow now? :) |
✅ Deployment SUCCESS |
✅ Deployment SUCCESS |
✅ Deployment SUCCESS |
✅ Deployment SUCCESS |
…ter understanding of what deployment/E2E failed/succeeded
✅ E2E tests SUCCESS |
✅ Deployment SUCCESS |
✅ E2E tests SUCCESS for commit ed670a4 previously deployed at https://nrn-v2-mst-aptd-gcms-lcz-sty-c1-btkq9fhw5.vercel.app |
✅ Deployment SUCCESS |
❌ E2E tests FAILED |
…o low (what matters is production)
✅ Deployment SUCCESS |
✅ E2E tests SUCCESS for commit a2b1d89 previously deployed at https://nrn-v2-mst-aptd-gcms-lcz-sty-c1-dp11f2oms.vercel.app |
✅ Deployment SUCCESS |
✅ Deployment SUCCESS |
✅ Deployment SUCCESS |
✅ Deployment SUCCESS |
dbfd4f8
to
a2b1d89
Compare
✅ Deployment SUCCESS |
✅ E2E tests SUCCESS for commit a2b1d89 previously deployed at https://nrn-v2-mst-aptd-gcms-lcz-sty-c1-n9ru06e1q.vercel.app |
Co-authored-by: Dhenain Ambroise <ambroise.dhenain@gmail.com>
https://app.asana.com/0/1136912812619441/1187144316166177
Allows to deploy a customer from the GitHub UI and from HTTP call to GitHub Actions.
The goal of this feature is to allow manual deployment of customers through GitHub UI, and through external HTTP calls.
See WORKFLOW_DISPATCH for advanced documentation.
Additionally, a few more improvements related to GHA have been done in this PR:
Important note:
It is not possible to use the manual trigger through NRN, because the github workflows must exist in the "main" github branch. NRN main branch is the documentation branch, and doesn't contain code-related actions.
This particular feature is usable only when making one of the preset your main branch (when forking NRN).
The API endpoint is usable from NRN directly though.
See https://github.saobby.my.eu.orgmunity/t/cant-trigger-workflow-manually/121740/52