ci: adding workflows to report deployment/pr info to GetDX #2066
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ju-Skinner
changed the title
pixelflips
approved these changes
Feb 18, 2025
ju-Skinner
approved these changes
Feb 18, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This introduces a few new workflows and workflow steps for GetDX reporting. The new
getdx-service-identificationworkflow will run on merge todevelop&&main(ensuring this is correct with the GetDX teamEDIT: This is correct), and will inform them of what services are affected by a PR merge.Calls about deployments are being made for
productionlevel deploys in thedeploy-releaseworkflows and are tied to the sites they create.These are new actions, so there may be some bugs to work out. If you run into issues please let us know on IPA.