ci.github: add preview-build workflow #6425
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes #6424
This new
preview-build
workflow triggers thepreview-build
workflows on thestreamlink/windows-builds
andstreamlink/streamlink-appimage
repos whenever something was pushed tomaster
and eitherpyproject.toml
,setup.py
,MANIFEST.in
orsrc/**
was modified:These two links are added to the run's summary markdown text, so users can find the build artifacts easily when clicking the workflow here. Unfortunately, direct links in the summary can't be included, as the workflow here merely triggers the workflows on the other repos. GitHub doesn't include a workflow run ID in its API response.
The docs have also been updated accordingly. I will remove the nightly workflows from the repos after this PR here was merged. The recent runs and their build artifacts should remain for 90 days (until expiration) when deleting workflow files.
I've checked and triggered the workflows using a GH PAT, but I don't know if
secrets.GITHUB_TOKEN
withpermissions.actions=write
also has the permissions to trigger a workflow on other repos. If it doesn't, then I will have to add a PAT for the @streamlinkbot and use that instead.Does the
on.push
config here look fine? Not 100% sure... Tags pushed should be ignored and the paths should be correct.