-
-
Notifications
You must be signed in to change notification settings - Fork 2.7k
Add Github workflow to allow for automatic preview releases #22367
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
Conversation
bf8567c
to
f9dfc98
Compare
fddc18f
to
1f1320c
Compare
This issue is in "needs review" but there has been no activity for 7 days. ping @matomo-org/core-reviewers |
Co-authored-by: Marc Neudert <marc.neudert@gmail.com>
1f1320c
to
aa63485
Compare
# TODO: remove manual dispatch after testing and enable cron | ||
workflow_dispatch: | ||
branches: | ||
- 5.x-dev | ||
#schedule: | ||
# - cron: '0 1 * * *' # 1am daily |
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.
Should we change that before merging or leave it in, so we can test that manually before having it run as cron?
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.
I would say we merge it as workflow_dispatch
and run it once manually before updating it to a schedule. Just so we don't have to wait for the first scheduled run to see if any of the recent repository changes has an unforeseen impact 🤔
Description:
Adds a new workflow that determines what the new preview version should be, updates the version file, runs the tests for the new version and on success publishes a preview release.
If any of the steps fail along the way the action stops and doesn't create a release.
This introduces 5.x-preview branch that is always reset to the top of 5.x-dev before the version number is increased and tests are run, it can technically be deleted as it will be recreated every time.
The check for code changes is done between the newest preview version tag and 5.x-dev, excluding the line that contains the version number change in core/Version.php.
We can consider extending the range of changes we want to ignore in a follow up.
We either need to merge this for testing after a code review or people can run this in their own forks.
Review