Skip to content

Conversation

@pmshaw15
Copy link

Replace the use of the term master branch with main instead throughout guidance. Also change readme standard to ensure that the branching strategy used by a project is included.

Copy link
Member

@johnwatson484 johnwatson484 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good, can see all references have been replaced.

There is an inconsistency of the use of main vs Main. That was also present in master vs Master so technically not a new issue. Should we correct that?

Should we make reference that we expect main to be the default name for new repos and explicitly address the master vs main discussion. Or by calling it main we're implicitly addressing it without need to call it out.

Also somewhat ironic that this repo uses master.

@pmshaw15
Copy link
Author

Thanks for reviewing @johnwatson484. Have changed the upper case instances to be lower case.

Next step will be to rename this repo's master branch to be main.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants