-
Notifications
You must be signed in to change notification settings - Fork 4.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add instructions for using Codespaces #60996
Conversation
I couldn't figure out the best area label to add to this PR. If you have write-permissions please help me learn by adding exactly one area label. |
Tagging subscribers to this area: @Anipik, @safern, @ViktorHofer Issue DetailsAlso updating our onCreateCommand script to store the current commit id. Developers can use this file to know which version was built during the prebuild.
|
Tagging subscribers to this area: @dotnet/runtime-infrastructure Issue DetailsAlso updating our onCreateCommand script to store the current commit id. Developers can use this file to know which version was built during the prebuild.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is it possible to run a script on first use? That could not only fix HEAD but also set up remotes properly to their fork (prompting for github ID if necessary)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Other than one comment and adding the command to reset to the pre build commit on creation of the codespace, looks good. Thanks!
…re-built container
- Add 4-core machines
CI failure is #61331. Merging. |
Also updating our onCreateCommand script to store the current commit id. Developers can use this file to know which version was built during the prebuild.