[ReenigneArcher]

Description

Consumers of org_sync currently need their own report script/upload steps, and community-file policies must enumerate every organization's .github repository. Add reusable reports and exact repository-name targeting.

• Add repository_names rules such as [".github"], scoped by organizations.json and optional rule-level organizations. Match names case-insensitively, skip absent matching repos, and retain custom-property/eligibility checks and exact-repository inputs. Reject globs, invalid/duplicate names, and mixing name selectors with explicit repository lists.
• Generate mode-aware summaries and JSON artifacts inside the composite action, including partial/fatal sync results and target PR URLs. Allocate separate temporary report files and unique artifact names for repeated invocations; expose report_file and artifact_name outputs.
• Document the selector and built-in reporting, alphabetize the example organization list, and align Markdown table pipes.

This provides the reusable functionality needed by LizardByte/.github#993.

Screenshot

Issues Fixed or Closed

Roadmap Issues

Testing

• npm test: passed, including 447 JavaScript tests, JUnit reporting, and repository-wide ESLint.
• Focused org-sync suite: 130 tests passed; all six org-sync modules have 100% statement, branch, function, and line coverage.
• Added 22 regression cases covering automatic organization-list expansion, missing matching repositories, scope/exclusion boundaries, invalid name selectors, preview/delivery reports, partial/fatal failures, and unique reports for repeated invocations.
• uvx yamllint -c ../.github/.yamllint.yml actions/org_sync/action.yml and git diff --cached --check: passed.
• Hosted CI and the consumer's credentialed dry run will validate the composite action's report/upload steps.

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

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 100.00%. Comparing base (d547130) to head (c4828dc).
✅ All tests successful. No failed tests found.

Additional details and impacted files

@@            Coverage Diff            @@
##            master      #351   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           17        18    +1     
  Lines         2398      2437   +39     
  Branches       403       422   +19     
=========================================
+ Hits          2398      2437   +39     

Flag	Coverage Δ
Linux	100.00% <100.00%> (ø)
PowerShell	100.00% <ø> (ø)
Windows	92.88% <100.00%> (+0.11%)	⬆️
macOS	100.00% <100.00%> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Files with missing lines	Coverage Δ
actions/org_sync/config.js	100.00% <100.00%> (ø)
actions/org_sync/report.js	100.00% <100.00%> (ø)

---

Continue to review full report in Codecov by Harness.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update d547130...c4828dc. Read the comment docs.

🚀 New features to boost your workflow:

• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.