-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
recreate CI - Status/Health - issue in runtime #701
Comments
We definitely should; the only problem is that due to a miscommunication with GitHub the issues haven't yet been transferred to the new repo. I guess that in this particular case it's probably worth creating a new item right away as there's not yet an established date for the issue transfer and real issues are trickling in. What about just renaming this item to CI status / health and copying over the old content (you have already included the link to the old CoreCLR item)? I can easily do that, I just want to make sure we're in agreement on that. |
I will just transfer that issue individually to this repository. |
Issue transfered as #702. |
I think that is fixed then. |
@dotnet/runtime-infrastructure will we have something like https://github.com/dotnet/coreclr/issues/27231 for the new repo?
Jobs are red again (PR testing and outerloop) and it would be nice to have an issue where you could find known failures fast.
The text was updated successfully, but these errors were encountered: