Align upstream-sync documentation with destination repository standards - #3
Draft
RolfMoleman with Copilot wants to merge 2 commits into
Draft
Align upstream-sync documentation with destination repository standards#3RolfMoleman with Copilot wants to merge 2 commits into
RolfMoleman with Copilot wants to merge 2 commits into
Conversation
Co-authored-by: RolfMoleman <106377191+RolfMoleman@users.noreply.github.com>
Copilot
AI
changed the title
Align upstream sync docs with destination standards
Align upstream-sync documentation with destination repository standards
Aug 21, 2026
Copilot created this pull request from a session on behalf of
RolfMoleman
August 21, 2026 18:43
View session
|
@copilot when I said upstream I meant the Microsoft repository |
Co-authored-by: RolfMoleman <106377191+RolfMoleman@users.noreply.github.com>
Author
Updated in commit |
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.
This update completes the upstream-sync follow-through by aligning repository-facing documentation and metadata with the destination fork. It ensures the merged upstream state is clearly represented in-project without behavioral code changes.
Repository metadata alignment
package.jsonrepository URL to point toDownAtTheBottomOfTheMoleHole/process-migratorso package metadata resolves to the correct canonical fork.Inline upstream status documentation
README.mddocumenting that this fork already includes the upstream SDK/toolchain modernization (TypeScript 5,azure-devops-node-api v17) and that usage/config guidance is maintained here.