-
-
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
Add an action that releases automatically when a change lands on the main branches #227
Conversation
…es automatically when a change lands on the main branches
✅ Deployment SUCCESS |
✅ Deployment SUCCESS |
✅ Deployment SUCCESS |
✅ Deployment SUCCESS |
✅ Deployment SUCCESS |
✅ Deployment SUCCESS |
❌ E2E tests FAILED for commit 9a929d1 previously deployed at https://nrn-v2-mst-aptd-at-lcz-sty-c1-346gevdv6.vercel.app |
✅ Deployment SUCCESS |
❌ E2E tests FAILED for commit 07a336f previously deployed at https://nrn-v2-mst-aptd-at-lcz-sty-c1-36a2p7pzu.vercel.app |
✅ Deployment SUCCESS |
✅ Deployment SUCCESS |
❌ E2E tests FAILED for commit 2242217 previously deployed at https://nrn-v2-mst-aptd-at-lcz-sty-c1-b3gvkbge6.vercel.app |
✅ Deployment SUCCESS |
✅ Deployment SUCCESS |
✅ E2E tests SUCCESS for commit 209866a previously deployed at https://nrn-v2-mst-aptd-at-lcz-sty-c1-9vlcz12v5.vercel.app |
…main branches #227 Improve doc (2) Improve doc Only trigger it on main branches Use version_tag (looks cleaner) Can't use fixed version, rollback Use fixed version Try another way Try ignoring #refs/heads/ Forgot stuff Simplify get branch Fix attempt Try to handle multiple "main" branches Bad commit id (wrong repo) Try using fixed version (safer than latest) Okay, gotta use latest, hasn't been released under a proper version Rety 1.1.0 Try using latest Remove code to see if warning keeps coming Alternative way to resolve current branch (3) Alternative way to resolve current branch (2) Alternative way to resolve current branch Print current branch Remove package.json:version (unnecessary) + add an action that releases automatically when a change lands on the main branches
…main branches #227 Improve doc (2) Improve doc Only trigger it on main branches Use version_tag (looks cleaner) Can't use fixed version, rollback Use fixed version Try another way Try ignoring #refs/heads/ Forgot stuff Simplify get branch Fix attempt Try to handle multiple "main" branches Bad commit id (wrong repo) Try using fixed version (safer than latest) Okay, gotta use latest, hasn't been released under a proper version Rety 1.1.0 Try using latest Remove code to see if warning keeps coming Alternative way to resolve current branch (3) Alternative way to resolve current branch (2) Alternative way to resolve current branch Print current branch Remove package.json:version (unnecessary) + add an action that releases automatically when a change lands on the main branches
❌ E2E tests FAILED for commit a4dda81 previously deployed at https://nrn-v2-mst-aptd-at-lcz-sty-c1-oxw9uk8eo.vercel.app |
No description provided.