Skip to content

ci(transparency): trigger transparency analyze #4371

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.

Sign up for GitHub

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

Merged
aeppling merged 3 commits into from
Oct 1, 2026
Merged

ci(transparency): trigger transparency analyze #4371

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
bf1906f
ci: start the transparency pipeline on release pull requests
Oct 1, 2026
91f0bbb
ci: restrict the transparency trigger to same-repository pull requests
Oct 1, 2026
364aef6
ci: require the next-release label on the transparency trigger
Oct 1, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
51 changes: 51 additions & 0 deletions .github/workflows/transparency.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,51 @@
name: Transparency

on:
pull_request:
types: [opened, synchronize, reopened, labeled]
branches: [master]

@KuSh KuSh Oct 1, 2026 •
edited
Loading

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Shouldn't we filter on Next Release name? I know the default branch has changed, but without more guard it can be triggered by anyone targeting master

@aeppling aeppling Oct 1, 2026

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

done on label below


permissions: {}

concurrency:
group: transparency-${{ github.event.pull_request.number }}
cancel-in-progress: true

jobs:
trigger:
if: >-
github.event.pull_request.head.repo.full_name == github.repository
&& github.head_ref == 'develop'
&& contains(github.event.pull_request.labels.*.name, 'next-release')
&& (github.event.action != 'labeled'
|| github.event.label.name == 'next-release')
runs-on: ubuntu-latest
timeout-minutes: 5
steps:
- name: Start transparency pipeline
env:
TOKEN: ${{ secrets.TRANSPARENCY_TRIGGER_TOKEN }}
PROJECT_ID: ${{ secrets.TRANSPARENCY_PROJECT_ID }}
PR_NUMBER: ${{ github.event.pull_request.number }}
PR_URL: ${{ github.event.pull_request.html_url }}
run: |
set -euo pipefail
if [ -z "${TOKEN:-}" ] || [ -z "${PROJECT_ID:-}" ]; then
echo "::notice::Transparency pipeline is not configured for this repository."
exit 0
fi
umask 077
printf '%s' "${TOKEN}" > token.txt
trap 'rm -f token.txt' EXIT
curl --silent --show-error --fail-with-body --max-time 60 \
--request POST \
--data-urlencode "token@token.txt" \
--data-urlencode "ref=main" \
--data-urlencode "variables[RTK_PR]=${PR_NUMBER}" \
--data-urlencode "variables[RTK_PR_URL]=${PR_URL}" \
"https://gitlab.com/api/v4/projects/${PROJECT_ID}/trigger/pipeline" > /dev/null
echo "::notice::Transparency pipeline started for PR #${PR_NUMBER}."
Loading