Change references from master to main#6259
Conversation
Forgind
left a comment
There was a problem hiding this comment.
I'd prefer to leave master as a trigger for a week or two until we've had a few successful insertions from main without manual interference. This seems unsafe if we need a hotfix but can't get anything into VS. Can dismiss if the balance is against me.
|
@Forgind I'm fine leaving this open until bare minimum one good VS insertion, but this PR should merge before any others. The outages today have slowed progress on this. /cc: @AR-May when you're around, can you run a pipeline build on main? You'll need to set /cc: @marcpopMSFT @ladipro @rokonec |
|
Not opposed to merging this before anything else, short of a very high-priority fix. As I understand the outages, we just have no way of running tests right now, so I don't think running the pipeline again would help more than just poking the current PR to run again. |
|
@Forgind Could just be me, but I haven't noticed the outage affecting CI tests. Kick em both I say ¯_(ツ)_/¯ |
|
Not CI but look at the reasons for our errors: |
|
@benvillalobos The VS insertion from main was successful. Crossed fingers helped. |
Fixes #6249
Context
This should finalize our master to main transition.
Changes Made
Remove master as a trigger.
exp/ branches should default to
mainfor optprof data now.Rename master to main in our primary readme file.
Notes
There are plenty of references to master in our documentation, but they'll forward to main so our links won't be broken.