-
Notifications
You must be signed in to change notification settings - Fork 165
Synchronization Workflow for Private Staging Repository #2971
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
base: main
Are you sure you want to change the base?
Conversation
samuel40791765
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is really nice
| deploy_environment_type: DeployEnvironmentType, | ||
| pipeline: pipelines.CodePipeline, | ||
| source: pipelines.CodePipelineSource, | ||
| source: pipelines.CodePipelineFileSet, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Minor question: What's the difference between Source and FileSet here?
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #2971 +/- ##
==========================================
- Coverage 78.48% 78.29% -0.19%
==========================================
Files 689 689
Lines 120840 120839 -1
Branches 16979 16973 -6
==========================================
- Hits 94838 94614 -224
- Misses 25108 25333 +225
+ Partials 894 892 -2 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
Description
Adds a workflow that will only actually execute in our private staging fork. Essentially it will take care of providing a daily synchronization mechanism for branches over to that fork. It will also allow for an on-demand workflow dispatch using the GitHub UI if you require a more up to date branch. This also transitions the CDK pipeline to actually always trigger on new commits. This might require recreation of the pipeline stack itself, as I believe the AWS CodeConnections links is not a good state after some actions taken a few months back in September.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license and the ISC license.