Use the 'pyTooling/SynchronizeForks' action

[paebbels-claude]

Changes

• .github/workflows/Synchronize.yml calls pyTooling/SynchronizeForks
  instead of carrying the algorithm. 60 lines of inline shell become:

        - name: 🔄 Synchronize Repositories
          uses: pyTooling/SynchronizeForks@v1
          with:
            github-token: ${{ secrets.GH_TOKEN }}

  The trigger, the schedule and the checkout are unchanged. targetOrganisation=Paebbels is dropped — the action
  defaults to ${{ github.repository_owner }}, which is Paebbels here. The ☑ Check GitHub API step moved into
  the action.

• No *.repos file changes. The configuration format is identical, so every fork and branch listed here is read
  exactly as before.

• What the run gains, from the action's own history: a missing <organisation>.repos file and a malformed line
  become counted errors instead of being ignored, a file without a trailing newline no longer drops its last
  repository, multi-line gh repo sync output survives into the error annotation, each organisation is a collapsible
  group, and the run ends with a summary plus a Not synchronized: list.

Documentation

• README.md says the algorithm lives in the action and this repository contributes the workflow and the
  configuration files. Steps to Setup shows the workflow snippet rather than a list of files to copy, and the
  configuration section points at the action's README as the authority.
• The inventory was stale and is regenerated from the *.repos files. It listed 10 OSVVM forks; there are 16. It
  had no VHDL section at all, so PoC was undocumented. It didn't distinguish the two disabled entries
  (OSVVM-AvalonMM, OSVVM-AvalonST) from the active ones, and it named no upstreams or branches. Each entry now
  reads <fork> ⇐ <upstream> — <branches>.
• Pipeline.png is kept and labelled as a screenshot of the previous implementation.

Others

• Every <upstream> in this repository's files was verified against GitHub: for all 24 entries,
  GET /repos/<upstream> resolves and GET /repos/Paebbels/<fork> reports exactly that repository as its parent.
  Nothing to correct — which matters, because the action reports the upstream in its progress and error output.

• Optional, not enabled here: create-missing-branches: true lets the action create a configured branch the fork
  doesn't have yet, from the upstream's branch head. It's off by default because it trusts the <upstream> field —
  and this repository's fields are the ones just verified above, so enabling it is a one-line addition whenever you
  want it.

• The action pins @v1. pyTooling/SynchronizeForks released
  v1.0.0, and its v1 major-version branch now
  carries the action. That branch is moved to each release by the action's own pipeline, so this workflow follows
  v1.x without being edited; a breaking v2 would need a deliberate change to @v2 here.

---

Related Issues and Pull-Requests

• pyTooling/SynchronizeForks#1 — the action, extracted from
  this repository's workflow.
• A matching conversion is proposed for VHDL/Synchronize.

🤖 Generated with Claude Code

https://claude.ai/code/session_01RnpaXYDwfNwnJrQew78j3f