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

Update base models, and do so with each "make composerupdate" #351

Merged
merged 2 commits into from
Aug 19, 2024

Conversation

forevermatt
Copy link
Contributor

Added

  • Revise Makefile to update base models after every composer update
    • Occasionally Yii updates their template for Active Record model files. It seems more helpful to see the effects of those changes in that same PR (where Yii was updated), rather than seeing them in a later, unrelated PR. Updating the base models only takes around 10 seconds, so it seems like a minimal time cost (percentage-wise) that we're adding to each composer update call.

Fixed

  • Update the base models (using our current version of Yii). Insignificant changes.

Occasionally Yii updates their template for Active Record model files.
It seems more helpful to see the effects of those changes in that same
PR (where Yii was updated), rather than seeing them in a later,
unrelated PR.

Updating the base models only takes around 10 seconds, so it seems like
a minimal time cost (percentage-wise) that we're adding to each composer
update call.
@forevermatt forevermatt requested a review from a team August 14, 2024 21:16
Copy link

sonarcloud bot commented Aug 14, 2024

@briskt
Copy link
Contributor

briskt commented Aug 15, 2024

  • Occasionally Yii updates their template for Active Record model files. It seems more helpful to see the effects of those changes in that same PR (where Yii was updated), rather than seeing them in a later, unrelated PR. Updating the base models only takes around 10 seconds, so it seems like a minimal time cost (percentage-wise) that we're adding to each composer update call.

This reminds me that you have significant automation in mail-admin. Would any of that be of value in IdP repos? The one I'm most curious about is the one that updates dependencies on every release.

@forevermatt
Copy link
Contributor Author

This reminds me that you have significant automation in mail-admin. Would any of that be of value in IdP repos? The one I'm most curious about is the one that updates dependencies on every release.

The auto-update-dependencies automation (when creating a new release) is actually minimally problematic, because we end up deploying dependencies to production before they have been tested on staging.

I think a better approach would be to simply include an "Update dependencies" step in the feature-branch PR checklist. (I'll be glad to share with you the details of Mail Admin's automated dependency updates, it just comes with some drawbacks.)

@forevermatt forevermatt merged commit cfef138 into develop Aug 19, 2024
3 checks passed
@forevermatt forevermatt deleted the feature/update-base-models branch August 19, 2024 15:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants