This repository has been archived by the owner on Jan 21, 2025. It is now read-only.
Update readme to add the disclaimer of not creating new PRs and issues #789
Conversation
This file contains 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
Update README.md to ask people don't create issues/PRs into cadl-ranch repo
lirenhe
requested review from
timotheeguerin,
iscai-msft,
lmazuel,
weidongxu-microsoft,
m-nash and
tadelesh
as code owners
|
weidongxu-microsoft
approved these changes
Jan 9, 2025
|
I will merge this PR if there is no concern by end of today. @lmazuel cc @sarangan12 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
As we completed the migration of cadl-ranch into spector, all new changes or issues should be created in microsoft/typespec repo and azure case should be added into typespec-azure repo.
Update the readme to add this disclaimer to suggest people not creating new PRs and issues in this repo.