-
Notifications
You must be signed in to change notification settings - Fork 76
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
Switch dotnet/scenario-tests
onto the full code flow
#4159
Milestone
Comments
We can do steps 1 and 2 immediately after #4158 and and have one-way flow only |
This was referenced Nov 21, 2024
The original issue body still mentions |
This was referenced Dec 4, 2024
dotnet/scenario-tests
onto the full code flow
Forward flow now works: dotnet/dotnet#123 |
The repo is now on the flat flow only |
premun
added a commit
that referenced
this issue
Feb 24, 2025
We have a pending TODO where we don't fill the `RequiredUpdates` yet. However, the merge policy check fails on an NRE if this is null. Example: https://github.com/dotnet/scenario-tests/pull/213/checks?check_run_id=37710832910 #3866 #4159
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Context
We have agreed that we want to start dogfooding the flat dependency flow by using the
dotnet/scenario-tests
repository.First, we need to implement #4158 though.
Goal
scenario-tests
via the current pipeline methodscenario-tests
to the VMRscenario-tests
repositoryscenario-tests
packages out of the VMRscenario-tests
packages inscenario-tests
's CIscenario-tests
depend on the VMR channel insteadThe text was updated successfully, but these errors were encountered: