chore(docs/cicd): make docs workflow secure#2986
Draft
AlexanderLanin wants to merge 2 commits into
Draft
Conversation
AlexanderLanin
requested review from
MaximilianSoerenPollak and
dcalavrezo-qorix
as code owners
github-project-automation
Bot
added this to
TLC - Technical Lead Circle and S-CORE Roadmap
|
The created documentation from the pull request is available at: docu-html |
lurtz
reviewed
Jun 16, 2026
lurtz
left a comment
lurtz
left a comment
Contributor
There was a problem hiding this comment.
in inc_someip_gateway I used a meta job, which depends on all the required ones and checks their status. Then you only need to configure that one as required in Github / Otterdog. More on that can be found at the pull request.
So far the approach in inc_someip_gateway worked nicely. I never had to touch the .eclipsefdn repo again.
IMHO we should consolidate the patterns being used. IIRC devcontainer, communication and baselibs are using merge queues as well.
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
2 participants
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.
Use new secure docs workflow split, where anything running bazel is treated as untrusted PR context. And that artefact is later picked up by a secure workflow running from main branch (therefore it will not work in this PR, similar to pull_request_target).
As a little byproduct, this makes score repo ready for merge queues! One of the first merge queue capable repos. As everything PR-related is now handled by on-pr workflow!