Razor release/insiders codeflow is blocked

[dkurepa]

Recently, razor made a new branch, release/insiders and made it flow to vmr 10.0.3xx (they also have a backflow)
These branches are not based on the previously flown branch so we have to do the flow manually.
Importantly, we can't do a backflow before we do a FF, because the 10.0.3xx VMR currently has the wrong branch of Razor in it, so we have to do a FF first

• FF unblocked
• BF unblocked

[jjonescz]

release/internal

Did you mean release/insiders? We also created this in roslyn. We are planning to snap like this every month, so it might be good to discuss how to do this better.

cc @phil-allen-msft @dotnet/roslyn-infrastructure

[jjonescz]

These branches are not based on the previously flown branch so we have to do the flow manually.

The branches should be based on previous commits, but I now realize I have merged flows that have a bit more commits from main (before the subscription switched), so that is probably causing the problem.

[dkurepa]

Insiders, yes my bad.
We're now working on a way for Maestro to make these --unsafe flow PRs on it's own, so we reduce the amount we need to intervene, so in theory you won't have to be careful around these

[jjonescz]

perhaps we could instead revert the bad flows:

• [release/10.0.3xx] Source code updates from dotnet/razor dotnet#5804
• [release/10.0.3xx] Source code updates from dotnet/roslyn dotnet#5805

and then let the new flow from insiders branch pick up

[dkurepa]

These branches are not based on the previously flown branch so we have to do the flow manually.

The branches should be based on previous commits, but I now realize I have merged flows that have a bit more commits from main (before the subscription switched), so that is probably causing the problem.

yup, if there were commits made on the base branch, and then they forward flew, it would cause this exception

[dkurepa]

perhaps we could instead revert the bad flows:

• [release/10.0.3xx] Source code updates from dotnet/razor dotnet#5804
• [release/10.0.3xx] Source code updates from dotnet/roslyn dotnet#5805

and then let the new flow from insiders branch pick up

I wouldn't recommend that, the reverts would technically be detected by Forward flows in the Codeflow algorithm, and that might lead to unwanted behavior

[jjonescz]

okay, I thought the codeflow would just check commits in the source manifest and those would be correct, but I guess it's more complicated than that