Skip to content

Add priority repos and MAX_REPOS=50 cap to rollout_codeql.sh - #1253

Merged
HarithaIBM merged 1 commit into
mainfrom
sk/rollout-codeql
Sep 18, 2026
Merged

HarithaIBM merged 1 commit into
mainfrom
sk/rollout-codeql

Conversation

@Sanjana-Kondalwade

Copy link
Copy Markdown
Collaborator

What type of PR is this? (check all applicable)

  • Refactor
  • Feature
  • Bug Fix
  • Optimization
  • Content Update

Category

  • zopen build framework
  • zopen package manager
  • Documentation
  • CI/CD
  • Tools

Description

Updates bulk-utils/rollout_codeql.sh to process repos in a controlled, prioritized order:

  • Adds a PRIORITY_REPOS array of 12 critical repos (gitport, makeport, curlport, gpgport, pinentryport, perlport, lessport, ncursesport, rpmport, dnf5port, vimport, autoconfport) that are always processed first.
  • Adds a MAX_REPOS=50 cap to limit the total number of repos processed per run.
  • Adds an is_priority() helper to avoid duplicates when building the final list.
  • Builds ORDERED_REPOS by prepending all 12 priority repos, then filling the remaining 38 slots from the full repo list (excluding priority repos already included).
  • The rest of the script (cloning, diff check, badge injection, commit, push, PR creation) is unchanged.

Related Issues

  • Related Issue #
  • Closes #

[optional] Are there any post-deployment tasks or follow-up actions required?

After this PR is merged, trigger the rollout_codeql CI workflow manually from main to begin rolling out CodeQL to all port repos in priority order.

@HarithaIBM HarithaIBM left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

LGTM, Sure, lets try this for few repos first

@HarithaIBM
HarithaIBM merged commit c2a5f22 into main Sep 18, 2026
3 of 4 checks passed
@HarithaIBM
HarithaIBM deleted the sk/rollout-codeql branch September 18, 2026 10:16
@Sanjana-Kondalwade
Sanjana-Kondalwade restored the sk/rollout-codeql branch September 18, 2026 10:30
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.

2 participants