github ci: also trigger build-tests on pull-requests #15
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Also trigger the CI build pipeline on pull-request actions. This is due to the CI not running on the branch when triggered from an action. This happens when bumping Gluon. As the ressources are not that much of an concern, trigger the build-test twice in worst-case. Signed-off-by: David Bauer <mail@david-bauer.net>
blocktrron
force-pushed
the
ci-run-on-pr
branch
from
b833e2c to
1061e09
Compare
|
AFAIK this won't help Possible workarrounds can be found here: https://github.com/peter-evans/create-pull-request/blob/main/docs/concepts-guidelines.md#workarounds-to-trigger-further-workflow-runs |
|
Please see 0fbc457 and put this PR into context. This is about performing the build-run action by opening the PR by a regular account. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Also trigger the CI build pipeline on pull-request actions. This is due
to the CI not running on the branch when triggered from an action. This
happens when bumping Gluon.
As the ressources are not that much of an concern, trigger the
build-test twice in worst-case.