You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -64,6 +64,7 @@ it's a good idea to check the previous link for any old or stalled insertions in
64
64
Update the `insertTargetBranch` value at the bottom of `azure-pipelines.yml` in the appropriate release branch. E.g., when VS 17.3 snapped and switched to ask mode, [this PR](https://github.com/dotnet/fsharp/pull/13456/files) correctly updates the insertion target so that future builds from that F# branch will get auto-inserted to VS.
65
65
66
66
### When VS `main` is open for insertions for preview releases of VS:
67
+
67
68
0. Disable auto-merges from `main` to **current** release branch, please make a change for the following file and create a pull request:
The repo is [here](https://dev.azure.com/dnceng/internal/_git/dotnet-fsharp), the CI is [here](https://dnceng.visualstudio.com/internal/_build?definitionId=499).
138
+
139
+
If something breaks in the CI there and you want to experiment, the general workflow is the following:
140
+
1. Make a branch
141
+
2. Make a change
142
+
3. Run the build from your branch. If needed, set the "skipTests" variable to "true" - can save time at this stage.
143
+
4. Once the problem and the fix is identified, make a PR to THIS (dotnet/fsharp) repo - it will propagate to the internal mirror just afterwards.
144
+
5. Delete all your work in the internal repo.
145
+
146
+
**DO NOT** try to push to the internal repo - this will mess up the flows. **DO NOT** create PRs to not confuse anyone.
147
+
148
+
You need the following permissions to do the above investigations:
0 commit comments