Rename `ci_master` flow to a `ci_main` or at least create a new duplicate `ci_main` flow

[Julian88Tex]

Feature Type

I'm interested in a new Task or Flow for CumulusCI.

Does your feature request solve a current problem?

Currently ci_master must be used to get the features of ci_master. Main organizations, like GitHub, are transitioning away from master/slave terminology.

Describe the solution you'd like

• Create ci_main as a flow that references the same functionality as ci_master so organizations have the option to use it.
• Additionally, could deprecate ci_master over time to help encourage organizations to switch off of this naming. Likely this would require a transition period and warning messages so that it does not create any mass breakage.

Describe alternatives you've considered

No response

Additional context

• https://www.zdnet.com/article/github-to-replace-master-with-main-starting-next-month/
• https://sfconservancy.org/news/2020/jun/23/gitbranchname/

[davidmreed]

Thanks for bringing this up, @Julian88Tex. We've kept that historical flow name around even as we've moved our own repos to use main.

I think we'll need to do what we've long thought about and introduce some type of flow aliasing to make this possible, but I love the idea of transitioning to ci_main. I'll make sure this is represented on our backlog.

[Julian88Tex]

@davidmreed thanks! Kind of related, might make sense to just do a search and see if anything else can be switched:

https://github.com/search?q=repo%3ASFDO-Tooling%2FCumulusCI%20master&type=code https://github.com/search?q=repo%3ASFDO-Tooling%2FCumulusCI%20slave&type=code

Looks like some references are to dependencies but they may already be providing alternate non-slave/master references.