Skip to content

drone: don't run the pipeline on pull_request (stop red PR builds)#7

Closed
cyberb wants to merge 1 commit into
masterfrom
drone-no-pull-request
Closed

drone: don't run the pipeline on pull_request (stop red PR builds)#7
cyberb wants to merge 1 commit into
masterfrom
drone-no-pull-request

Conversation

@cyberb

@cyberb cyberb commented Jul 8, 2026

Copy link
Copy Markdown
Member

Problem

Every pull_request build is red even though build/test pass. The artifact step uses the artifact_key secret, which drone withholds from pull_request events, so it always fails at that step — a spurious red check on every PR.

Fix

Drop pull_request from the pipeline trigger, so it runs only on push and tag. PRs still get a green branch push build; the noisy failing pull_request build is gone.

Matches the convention already used across the recently-updated syncloud projects (navidrome, files, platform, …). Validated with drone jsonnet + drone lint.

pull_request builds are red anyway: the artifact step uses the
artifact_key secret, which drone withholds from pull_request events, so
every PR build fails at that step even though build/test pass. Drop the
pull_request trigger so the pipeline runs only on push and tag.
@cyberb

cyberb commented Jul 8, 2026

Copy link
Copy Markdown
Member Author

Folded into #6.

@cyberb cyberb closed this Jul 8, 2026
@cyberb cyberb deleted the drone-no-pull-request branch July 8, 2026 07:03
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant