Skip to content

ci: give the dev branch the same workflow coverage as main - #60

Open
roshan-ku wants to merge 1 commit into
OpenVisualCloud:mainfrom
roshan-ku:ci/run-workflows-on-dev
Open

ci: give the dev branch the same workflow coverage as main#60
roshan-ku wants to merge 1 commit into
OpenVisualCloud:mainfrom
roshan-ku:ci/run-workflows-on-dev

Conversation

@roshan-ku

Copy link
Copy Markdown
Contributor

Summary

Gives the dev branch the same CI/security workflow coverage as main.

Changes

Workflow Change
Continuous Integration push now also triggers on dev
Pull Request pull_request now also matches a dev base branch
OpenSSF Scorecard push now also triggers on dev; publish_results is gated to the default branch, which is the only branch the Scorecard API accepts results from
Daily Build build, afl-fuzz and libfuzzer fan out over a branch: [main, dev] matrix (fail-fast: false), check out refs/heads/<branch> and upload branch-suffixed artifacts so names don't collide
Coverity Scan Same main/dev matrix; the scanned commit is resolved and passed to upload-sarif via ref/sha so dev findings aren't attributed to main

Scheduled workflows always run on the default branch, so a matrix is the only way to give dev equivalent nightly/weekly coverage — hence the explicit branch checkout rather than github.sha.

scan_on_demand.yml already accepts a branch input and needed no change.

Notes for reviewers

  • Scheduled runs now use roughly double the CI minutes.
  • workflow_dispatch on Daily Build / Coverity now scans both main and dev regardless of the selected ref.
  • If dev becomes a merge target, its branch protection rules need the new required status checks added.

Validation

  • All six workflow files parse as YAML.
  • actionlint reports no issues.

Add dev to the push filters of Continuous Integration and OpenSSF
Scorecard, and to the pull_request base filter of the Pull Request
workflow.

Scheduled workflows only ever run on the default branch, so Daily Build
and Coverity Scan now fan out over a main/dev matrix, check out the
matrix branch explicitly and tag their artifacts with it. Coverity
passes the scanned ref and sha to upload-sarif so dev findings are not
attributed to main, and Scorecard only publishes results from the
default branch, which is all the Scorecard API accepts.
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