-
Notifications
You must be signed in to change notification settings - Fork 483
DataModel: make V0s IsStandard explicit #13937
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
Conversation
This makes the check more explicit to really have a standard v0. If analysers just ask for this bit, for example they still would get tpc-only v0s. @ddobrigk
|
REQUEST FOR PRODUCTION RELEASES: This will add The following labels are available |
Thanks a lot @f3sch , this makes custom use of V0s much less error-prone, as |
|
Error while checking build/O2/fullCI for 12d6425 at 2025-02-21 23:09: Full log here. |
|
@jgrosseo if you agree, please merge. |
|
Error while checking build/O2/fullCI_slc9 for 12d6425 at 2025-02-21 11:46: Full log here. |
|
pinging @jgrosseo. |
This makes the check more explicit to really have a standard v0. If analysers just ask for this bit, for example they still would get tpc-only v0s. @ddobrigk