-
Notifications
You must be signed in to change notification settings - Fork 7
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 GitHub environment URLs #821
Comments
This was referenced Oct 27, 2022
seanh
referenced
this issue
in hypothesis/workflows
Oct 24, 2022
Part of https://github.com/hypothesis/workflows/issues/3 and https://github.com/hypothesis/workflows/issues/4. Add a new `deploy.yml` shared workflow which is similar to the existing `eb-update.yml` workflow but allows the caller to provide the GitHub environment name and URL as inputs. This will enable us to change the caller workflows in each of our app repos one-by-one to call the new `deploy.yml` workflow instead of `eb-update.yml`, correcting the GitHub environment names and adding environment URLs to each app repo one by one. Once all app repos have been moved over we can then finally delete the original `eb-update.yml`.
seanh
referenced
this issue
in hypothesis/workflows
Oct 24, 2022
Part of https://github.com/hypothesis/workflows/issues/3 and https://github.com/hypothesis/workflows/issues/4. Add a new `deploy.yml` shared workflow which is similar to the existing `eb-update.yml` workflow but allows the caller to provide the GitHub environment name and URL as inputs. This will enable us to change the caller workflows in each of our app repos one-by-one to call the new `deploy.yml` workflow instead of `eb-update.yml`, correcting the GitHub environment names and adding environment URLs to each app repo one by one. Once all app repos have been moved over we can then finally delete the original `eb-update.yml`.
seanh
referenced
this issue
in hypothesis/workflows
Oct 25, 2022
Part of https://github.com/hypothesis/workflows/issues/3 and https://github.com/hypothesis/workflows/issues/4. Add a new `deploy.yml` shared workflow which is similar to the existing `eb-update.yml` workflow but allows the caller to provide the GitHub environment name and URL as inputs. This will enable us to change the caller workflows in each of our app repos one-by-one to call the new `deploy.yml` workflow instead of `eb-update.yml`, correcting the GitHub environment names and adding environment URLs to each app repo one by one. Once all app repos have been moved over we can then finally delete the original `eb-update.yml`.
This was fixed by #818 |
This was referenced Oct 27, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Depends on #820.
GitHub lets deployment workflows associate a single URL with each environment and handily links to this URL in various places where environments and deployments to environments appear in the GitHub UI.
This would be a useful feature to have so we should add it to our deployment workflows. Unfortunately our deployment workflows don't currently create a separate GitHub environment for each Elastic Beanstalk environment, so we need to fix #820 before we can do this
The text was updated successfully, but these errors were encountered: