You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It looks like the pipeline came after the examples.
So the pipeline version is the quick way and the examples are the more detailed approach.
I started using it in LM-Commons and that where I noticed it was different than in Laminas' repos. The examples need to be updated as well, like the version of the checkout which is now at v4.
The only difference between the two examples is in the use of secrets.ORGANIZATION_ADMIN_TOKEN vs secrets.GITHUB_TOKEN as the token used in the Release step.
The version in the 'workflow-automatic-releases' repo looks the same as the release-on-milestone-closed-triggering-release-event.yml example.
So I agree that the README should propose two approaches
Quick and easy, using the pipeline from 'workflow-automatic-releases'
The more detailed examples, updated, that users are free, as always, to modify to suit their needs
Bug Report
Summary
The workflows in the example folder that one is supposed to copy to a repository, are not the same as what is currently used in repositories.
Current behavior
The example workflows have detailed steps for the release job, and are out of date.
Expected behavior
The workflows currently used in laminas/mezzio repos refer to the shared workflow. The examples should be updated.
release-on-milestone-closed.yml
:Do we still need
release-on-milestone-closed-triggering-release-event.yml
?If not, then the README.md file needs to be update to remove the reference to it.
The text was updated successfully, but these errors were encountered: