Repository navigation
chore(qnx-build): bump checkout action - #144
Merged
Merged
Conversation
lurtz
marked this pull request as ready for review
July 23, 2026 16:42
lurtz
requested review from
AlexanderLanin,
MaximilianSoerenPollak,
PiotrKorkus,
dcalavrezo-qorix,
nradakovic,
opajonk and
pawelrutkaq
as code owners
July 23, 2026 16:42
lurtz
changed the title
AlexanderLanin
approved these changes
Jul 23, 2026
AlexanderLanin
changed the title
This file contains hidden or 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
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.
actions/checkoutgot a security update and should be bumped.I tried to make the QNX workflow run with the
pull_requesttrigger from forks, but in that case there is no access to any secrets at all. This left me withpull_request_targetas the only option. However I recommend to have the QNX workflow as opt-in via labels in pull requests and to run it in the merge queue. Most of the time the merge queue is enough.Using labels and workflow approval as a double opt-in should hopefully act as a strong enough safeguard.
More reading:
This PR also bumps the devcontainer image version and add the Github Action extension as an easy drive-by fix.