trinodb/trino

dependabot-originating builds fail due to lack of secrets

Open

#28,176 opened on Feb 9, 2026

View on GitHub
 (2 comments) (0 reactions) (0 assignees)Java (2,678 forks)batch import
good first issuemaintenancetest

Repository metrics

Stars
 (9,113 stars)
PR merge metrics
 (Avg merge 6d 3h) (251 merged PRs in 30d)

Description

There is a problem with dependabot-initiated PR builds. The build attempt to run jobs requiring secrets and fails as the secrets are not found Example: https://github.com/trinodb/trino/actions/runs/21819342270/job/62948556703?pr=28175 (#28175)

My understanding is that dependabot-originated flows have access to repo vars, but they don't see repo secrets except those configured for dependabot itself. Given job conditions being has-var || has-secret, this leads to build failures.

proposed solution

Change job conditions to be "(has-var && !dependabot-originated) || has-secret"

Contributor guide

Research direction
Locate the job condition in the workflow YAML that uses `has var || has secret` and modify it to exclude dependabot triggered runs when only `has var` is true. The new condition should be `(has var && !dependabot) || has secret`.
Tech stack
javagithub actions
Domain
ci cddevops
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitGitHub Actions
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60