Skip to content

ci: don't run membrowse workflows on forks#10566

Merged
dgarske merged 1 commit into
wolfSSL:masterfrom
julek-wolfssl:membrowse-fork-guard
Jun 1, 2026
Merged

ci: don't run membrowse workflows on forks#10566
dgarske merged 1 commit into
wolfSSL:masterfrom
julek-wolfssl:membrowse-fork-guard

Conversation

@julek-wolfssl
Copy link
Copy Markdown
Member

The membrowse report job runs on a nightly schedule and would also fire on any fork with Actions enabled, burning fork CI minutes and reporting fork builds to the membrowse backend. Likewise the onboard workflow can be dispatched on a fork.

Guard the jobs in both workflows with if: github.repository_owner == 'wolfssl', matching the existing fork guard in tls-anvil.yml and coverity-scan-fixes.yml. The schedule is left unchanged.

Copilot AI review requested due to automatic review settings June 1, 2026 15:47
@julek-wolfssl julek-wolfssl self-assigned this Jun 1, 2026
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull request overview

This PR updates the Membrowse GitHub Actions workflows to avoid running (and reporting to the Membrowse backend) when triggered from forks, aligning with existing fork-guard patterns used in other CI workflows in this repo.

Changes:

  • Add a fork guard (if: github.repository_owner == 'wolfssl') to the scheduled Membrowse report workflow jobs.
  • Add the same fork guard to the workflow-dispatch Membrowse onboarding workflow jobs.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 4 comments.

File Description
.github/workflows/membrowse-report.yml Adds a job-level fork guard to prevent scheduled/adhoc Membrowse reporting from running on forks.
.github/workflows/membrowse-onboard.yml Adds a job-level fork guard to prevent onboarding workflow dispatch from running on forks.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment thread .github/workflows/membrowse-report.yml
Comment thread .github/workflows/membrowse-onboard.yml
Comment thread .github/workflows/membrowse-report.yml
Comment thread .github/workflows/membrowse-onboard.yml
Forks with Actions enabled would otherwise run the membrowse build matrix on push/workflow_dispatch and report fork builds to the membrowse backend. Guard the jobs in both workflows with github.repository_owner == 'wolfssl' (combined with the existing draft check in the report workflow), matching tls-anvil.yml and coverity-scan-fixes.yml.

Also default the analyze/onboard matrix to '[]' so strategy expansion does not error when load-targets is skipped on forks or draft PRs.
@julek-wolfssl julek-wolfssl force-pushed the membrowse-fork-guard branch from 49c55f4 to 2703458 Compare June 1, 2026 16:09
@github-actions
Copy link
Copy Markdown

github-actions Bot commented Jun 1, 2026

MemBrowse Memory Report

No memory changes detected for:

@dgarske
Copy link
Copy Markdown
Member

dgarske commented Jun 1, 2026

Jenkins retest this please: "PRB-fips-repo-and-harness-test-v3-part2 completed: FAILURE"

@dgarske dgarske merged commit aec2756 into wolfSSL:master Jun 1, 2026
449 checks passed
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.

3 participants