Skip to content
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

feat: forward parent lifecycles to child stages defined on the module #68

Merged
merged 1 commit into from
Mar 14, 2024

Conversation

srevinsaju
Copy link
Owner

In scenarios where lifecycles are defined on the module level, there was an issue preventing the same lifecycle phases from being applied to the child modules. This was very inconvenient when reusing multiple modules and the caller may have custom lifecycle phases, but the module's are not owned by the caller to make changes

Copy link

codecov bot commented Mar 14, 2024

Codecov Report

Attention: Patch coverage is 88.46154% with 3 lines in your changes are missing coverage. Please review.

Project coverage is 62.05%. Comparing base (aa2632a) to head (9fd8308).
Report is 2 commits behind head on v2.

Files Patch % Lines
internal/ci/module_run.go 82.35% 2 Missing and 1 partial ⚠️
Additional details and impacted files
@@            Coverage Diff             @@
##               v2      #68      +/-   ##
==========================================
+ Coverage   61.95%   62.05%   +0.09%     
==========================================
  Files         104      104              
  Lines        6903     6920      +17     
==========================================
+ Hits         4277     4294      +17     
  Misses       2345     2345              
  Partials      281      281              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@srevinsaju srevinsaju force-pushed the feature/module-lifecycle-forwarding branch 2 times, most recently from b26aeab to c7c535e Compare March 14, 2024 07:59
In scenarios where lifecycles are defined on the module level, there was an issue preventing the same
lifecycle phases from being applied to the child modules. This was very inconvenient when
reusing multiple modules and the caller may have custom lifecycle phases, but the module's
are not owned by the caller to make changes
@srevinsaju srevinsaju force-pushed the feature/module-lifecycle-forwarding branch from c7c535e to 9fd8308 Compare March 14, 2024 09:26
@srevinsaju srevinsaju merged commit 32bbbd7 into v2 Mar 14, 2024
9 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant