Repository navigation
Clarify canonical Git remote URL identity - #5685
Merged
Yuchao Yan (msyyc) merged 1 commit intoOct 14, 2026
Merged
Yuchao Yan (msyyc) merged 1 commit into
Yuchao Yan (msyyc) merged 1 commit into
Conversation
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Yuchao Yan (msyyc)
added a commit
that referenced
this pull request
Oct 14, 2026
## Summary Make subsequent RPaaS migrations smoother without broadening RPaaS restrictions to ordinary ARM or weakening validation/recovery gates. This is a standalone, skill-only follow-up to the first `ExtensionResourcePathPattern` migration in #5682 and promotion in #5684. ## Process findings and changes | Observed evidence | Skill correction | | --- | --- | | Intake initially stopped because no automatic native RPaaS selector was established. The accepted continuation used existing explicit lint enablement, default-disabled, with ordinary ARM counterexamples. Upstream RPaaS registration had been flattened to catalog `common`/`Both`. | Establish upstream audience separately from catalog eligibility. Consider supported native selection, an independently justified broader guideline, or documented external opt-in before classifying. Record mixed-audience limitations; preserve genuine uncertainty stops. | | The full generic corpus selected 468 projects, compiled 462, and left six failures. Target `0/0` reflected a default-disabled rule and ordinary ARM selection, not RPaaS parity. | Carry actual validator/native activation profiles into migration notes, promotion, and both reviews. Require enabled focused evidence and appropriate activation integration controls; retain required representative/full regression runs and disclose audience, version, diagnostic-unit, and source-identity limits. | | Development review reproduced two warnings for one authored operation-template endpoint, including a template companion. Four focused regressions corrected the diagnostic unit. | Check rule-owned HTTP/template traversal and exact endpoint counts/targets before expensive corpus runs, while retaining the exclusion of framework-only tests. | | Promotion documentation regeneration exited successfully but did not load the authored rule Markdown until supported compiler `docs`/`fileRef` metadata was added. | Verify authored-file binding and generated rationale/examples, not merely a successful regeneration or index entry. | | A quiet successful lint command produced no `Tee-Object` receipt file. Guessed config paths and a stale readiness budget mirror also caused avoidable handoff failures. | Capture empty raw output independently, derive paths from the actual checkout, and acknowledge authoritative later scoped grants without inventing stale-mirror prerequisites. Preserve exit statuses, counters, fingerprints, and failed evidence. | The reusable audience contract lives in rule intake; development, queue handoffs, and promotion link to it rather than duplicating a new RPaaS detector. Promotion also checks library/default/recommended/`all` activation, including automatic `all` behavior, and preserves every existing rule's enablement. ## Evidence and boundaries - The reviewed source's [migration evidence](https://github.com/Azure/typespec-azure/blob/99d04f1c7311c5919993dfbb0b0a8d8168d9ce70/packages/typespec-lintdiff/test/fixtures/ExtensionResourcePathPattern/migration.md) documents the native opt-in contract, ordinary ARM scope distinction, template regression, corpus limitations, and intentional diagnostic-unit/version differences. - The original stop, accepted continuation, failed-command receipts, scoped grants, and handoffs remain in the coordinating session's durable process records. Those operational artifacts are not committed. - Existing capabilities/reviewer ownership, immutable-source review, finite recovery authorization, and `no-valid-comments` termination already cover the runtime/review portions of the run and remain unchanged. The earlier optional `.git` repository-identity clarification remains separate in #5685. - No rule/package files, completed migration commits, later promotion changes, catalog schema, new worker flags, production audience detectors, dependencies, release entries, or generated outputs are changed. This PR does not claim production RPaaS corpus parity or re-review subsequent rule-PR heads. ## Validation - Reviewed the complete six-file Markdown diff against fetched canonical `feature/lintdiff-migration-new` base `527a585925e61bd782e61cce9127e235e555ea91`, including linked native-test responsibility and recovery/ownership contracts. - Ran Prettier write/check on only the six explicit changed files using already-prepared repository tooling; all passed. - Verified 76 relative Markdown file references and all new audience-contract anchors. - `git diff --check` passed. - No dependency installation, submodule setup, package/corpus builds/tests, repository-wide formatting, or recursive review loop was needed for this documentation-only update. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Yuchao Yan (msyyc)
marked this pull request as ready for review
October 14, 2026 06:54
Yuchao Yan (msyyc)
requested review from
Mark Cowlishaw (markcowl),
Timothee Guerin (timotheeguerin) and
Jeff Fisher (xirzec)
as code owners
October 14, 2026 06:54
Yuchao Yan (msyyc)
merged commit Oct 14, 2026
3e43759
into
feature/lintdiff-migration-new
3 checks passed
Yuchao Yan (msyyc)
deleted the
skills/lintdiff-remote-identity-extension
branch
October 14, 2026 06:54
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
1 participant
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.
Evidence
During the ExtensionResourcePathPattern queue, a publication preflight rejected the verified canonical remote https://github.com/Azure/typespec-azure solely because it lacked a .git suffix (command103). GitHub repository identity and push permission were already established, the reviewed content was unchanged, and no publication operation had been attempted. Independent read-only reconciliation confirmed the existing binding and permitted the next authorized action.
Change
Clarify the shared publication preflight: the optional .git suffix does not change the resolved owner/repository. Preserve actual effective push URL/refspec recording, canonical GitHub metadata and permission checks, phase ownership, and all duplicate-safe recovery rules. This does not authorize retries or weaken any content, review, validation, or publication gate.
Scope and validation
One skill-documentation file only, on a dedicated branch based on the freshly fetched canonical feature/lintdiff-migration-new ref. Explicit-file Prettier and git diff --check passed. The initial fresh-worktree formatter could not load the absent core plugin; the existing prepared promotion formatter/config was used instead, with no dependency installation or submodule setup. No rule/package/corpus changes or generated artifacts. Primary PRs #5682 and #5684 are untouched.