Rename default branch from `master` to `main`

[AlejandroFernandezLuces]

As title says.

Suggested in https://github.com/ansys-internal/pymechanical-meshworkflows/pull/51#discussion_r1905519900

This change is easy, but surely will break stuff in third repos. Maybe a migration plan should be defined?

[RobPasMue]

Definitely needs a migration plan. I think what was suggested works:

• Having master and main as two separate branches. Make main the default and sync back master during the migration period.
• Leave it as is for several months and work with the various libraries using this to adapt
• After migration on libraries is complete, completely deprecate master and freeze it.
• Eventually, deletion of master. I'm worried about backwards compatibility here for libraries that have already released versions using it... so this point is TBDetermined.

[SMoraisAnsys]

@AlejandroFernandezLuces I may have missed that info but can we start moving to main now ? :) I just checked and it seems that main is getting synchronized with master so I was wondering if we could start the migration.

[AlejandroFernandezLuces]

Right now the main branch is the default one, we are syncronizing master with main just for retrocompatibility reasons. Have you had any issues with the repo? Maybe I've done something wrong.

This is the syncing logic we have in place:

example-data/.github/workflows/sync-master.yml

Lines 25 to 30 in cd76c27

	- name: Sync master with main
	run: |
	git checkout master
	git pull origin master
	git merge origin/main --no-edit
	git push origin master

[SMoraisAnsys]

Right now the main branch is the default one, we are syncronizing master with main just for retrocompatibility reasons. Have you had any issues with the repo? Maybe I've done something wrong.

This is the syncing logic we have in place:

example-data/.github/workflows/sync-master.yml

Lines 25 to 30 in cd76c27

   - name: Sync master with main 
     run: | 
       git checkout master 
       git pull origin master 
       git merge origin/main --no-edit 
       git push origin master

No issues at all. I just wanted to know if we should wait a bit more because there were some tests going on or if we could do the changes. I'll apply that in pyaedt then :)

[AlejandroFernandezLuces]

I think this issue can be closed, since the migration has been done. If needed, let's open another issue for the master deprecation plan.