[ReenigneArcher]

Description

The roadmap dropdown currently discovers repositories from two hard-coded organizations and sorts names case-sensitively. Read the default organization list from LizardByte/.github/organizations.json so all registered organizations are included, and sort canonical organization/repository labels without regard to capitalization.

Keep the optional comma-separated override for manual runs, the archived-repository filter, and the existing daily regeneration and issue-labeling behavior. Registry and repository API failures stop the update rather than publishing a partial list.

Screenshot

Issues Fixed or Closed

Roadmap Issues

Testing

• actionlint and yamllint passed for the modified workflow; git diff --check passed.
• Executed both inline github-script steps extracted from the YAML in a temporary Node harness. Verified registry defaults, trimmed manual overrides, invalid registry rejection, paginated discovery, canonical labels, archive filtering, duplicate removal, mixed-case sorting, and API error propagation.
• Exercised the scripts against a live public GitHub inventory: 62 active repositories across all five registered organizations, including the transferred SunshineStream and Themerr projects.
• The repository has no standalone test harness; validation uses the actual inline scripts and the existing pull-request workflow preview rather than adding another test framework. The hosted pull-request preview passed and generated all 62 options in the expected order without creating a bot PR.

Type of Change

• feat: New feature (non-breaking change which adds functionality)
• fix: Bug fix (non-breaking change which fixes an issue)
• docs: Documentation only changes
• style: Changes that do not affect the meaning of the code (white-space, formatting, missing semicolons, etc.)
• refactor: Code change that neither fixes a bug nor adds a feature
• perf: Code change that improves performance
• test: Adding missing tests or correcting existing tests
• build: Changes that affect the build system or external dependencies
• ci: Changes to CI configuration files and scripts
• chore: Other changes that don't modify src or test files
• revert: Reverts a previous commit
• BREAKING CHANGE: Introduces a breaking change (can be combined with any type above)

Checklist

• Code follows the style guidelines of this project
• Code has been self-reviewed
• Code has been commented, particularly in hard-to-understand areas
• Code docstring/documentation-blocks for new or existing methods/components have been added or updated
• Tests have been added or updated for new or modified functionality, including regression tests for bug fixes

AI Usage

See our AI usage policy.

• AI tools were used while preparing this PR

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud