-
Notifications
You must be signed in to change notification settings - Fork 10.3k
Add CI configurations for build.cmd in sub-areas #12029
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
Labels
area-infrastructure
Includes: MSBuild projects/targets, build scripts, CI, Installers and shared framework
Done
This issue has been fixed
Comments
No, this is just a sub part. I'm still writing the full issue. |
|
How do I cancel pinging someone? 😆 |
4 tasks
Reassigning because you're already working on something very much like this @mkArtakMSFT |
@mkArtakMSFT can this now be closed? |
Yes. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
area-infrastructure
Includes: MSBuild projects/targets, build scripts, CI, Installers and shared framework
Done
This issue has been fixed
The proposal is to add CI configurations to run the build.cmd/build.sh in sub-areas such as Components, Installers, SignalR, etc to ensure the expected dev workflows, such as restore and build, remain aligned to the contributor guidelines.
The text was updated successfully, but these errors were encountered: