Repository navigation
ci: support multiple organizations in central maintenance - #1000
Merged
Merged
Conversation
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.



Description
Central maintenance now discovers repositories through
organizations.jsoninstead of assuming the controller owns every target. Stale issues, license updates, CPM profiles, and Pinact use canonical owners and repository names. Pinact supports unambiguous short-name dispatch inputs. The build-deps updater uses explicitowner/repositorychoices; shared build-deps releases stay in LizardByte.GitLab mirroring keeps existing LizardByte paths and automatically creates subgroups for the other registered organizations, such as
lizardbyte/sunshinestream. After a GitHub transfer, it verifies the existing mirror's immutable GitHub identity and transfers the same GitLab project into its subgroup, preserving history and settings. Qualified exclusions contain only repositories currently owned by the registered organizations. Namespace checks handle same-name repositories, while private visibility is verified before transfers and Git pushes. One failed repository does not stop the remaining mirrors.The existing GitLab API credential needs subgroup creation and project-transfer permissions under
lizardbyte, in addition to its existing project/import permissions. The SSH identity needs inherited push access. Existing archived GitLab mirrors are reported for manual handling. Provisioning runs in the existing mirror workflow; no GitLab resources were changed while preparing this PR.Screenshot
Issues Fixed or Closed
Roadmap Issues
Testing
node --test: 209 tests passed. A read-only discovery preview also passed against all five registered GitHub organizations. Added coverage for cross-org discovery, property selection, qualified/ambiguous targets, subgroup creation races, immutable mirror identity, private visibility, asynchronous project transfers, and failure isolation.Actionlint 1.7.12, yamllint 1.38.0, ShellCheck 0.11.0, Bash syntax validation, and
git diff --checkpassed. Actionlint's embedded shellcheck/pyflakes integrations were disabled; the extracted mirror shell script was checked separately with ShellCheck. GitLab API behavior is covered with mocked responses; live GitLab credential permissions and actual namespace/project operations have not been exercised. The updated build-deps workflow also passed actionlint and yamllint, and the reduced mirror-exclusion JSON parsed successfully. Hosted CI and Sonar reanalysis are pending for the latest push.Type of Change
Checklist
AI Usage
See our AI usage policy.