Skip to content

Conversation

jrfnl
Copy link
Collaborator

@jrfnl jrfnl commented Sep 20, 2025

The workflows currently contain two jobs which build the PHAR files. This means that any changes to the steps in these jobs have to be made in two places.

With this in mind, it makes sense to change the PHAR building to a reusable workflow, which can then be used by both jobs. With this change, any changes to the steps of the job will only need to be made in one place.

This commit makes it so.

The workflows currently contain two jobs which build the PHAR files.
This means that any changes to the steps in these jobs have to be made in two places.

With this in mind, it makes sense to change the PHAR building to a reusable workflow, which can then be used by both jobs.
With this change, any changes to the steps of the job will only need to be made in one place.

This commit makes it so.
@jrfnl jrfnl added this to the 1.4.x Next milestone Sep 20, 2025
@jrfnl
Copy link
Collaborator Author

jrfnl commented Sep 20, 2025

Note: the branch protection will need a small update for the changed job name.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging this pull request may close these issues.

1 participant