Skip to content

Reconcile VSCode-Server-DotNetCore in the Hub After Its Resync #1899

Closed

Description

@ptr727

VSCode-Server-DotNetCore was resynced to hub main 4566946 (2.0.685) through ptr727/VSCode-Server-DotNetCore#127, #128, #129, #130, and #131, all merged to develop. The hub-side records still describe the old state.

To Do

  • Registry: registry/repos.json driftNotes for VSCode-Server-DotNetCore reads "Separate publish-docker-readme-task for the Hub overview." The repo now calls the hub's publish-docker-readme-task.yml from its publish-release.yml, and no local copy remains, so delete the note.
  • Rollout: docs/reusable-workflows.md Stage 4 "VSCode-Server-DotNetCore (vanilla Docker only)", and the merge-bot and gate adoption items for this repo, can be ticked once main carries the stubs. That happens after the maintainer's develop -> main promotion. Regenerate reports/workflow-reuse.md in the same change.
  • Audit report: re-run spec/audit.py VSCode-Server-DotNetCore against main after the promotion, and commit reports/vscode-server-dotnetcore/audit.md. The last develop-branch run, 2026-09-26T13:44:31Z at hub 4566946, reports one finding, down from 57. That finding is the Docker Hub short description, which the readme task sets from the About text on the next main publish. Before the promotion, the audit also shows the expected branch overlap on the five retired task workflows.
  • Carry the code-review skill bootstrap to seven repos whose Copilot reviews never state coverage #1815: the coverage symptom is gone for this repo. Every Copilot round after the skills tree reached develop reported coverage=full or carried:full.

Local decisions taken during the resync, recorded for the audit reader:

  • The maintainer chose the fleet standard over keeping two local AGENTS.md rules: leave human-authored comments exactly as written, and diff main against develop for staleness.
  • repo-config/ruleset-develop.json and ruleset-main.json were pre-rename copies of the hub's develop.json and main.json, and were deleted along with the rest of repo-config/.
  • The Dockerfile moved to Docker/Dockerfile for the hub Docker core. This is filed separately as the undocumented-path issue.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    choreRegistry, labels, rollout, and other fleet housekeeping

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions