Skip to content

Conversation

Morganov
Copy link
Member

@Morganov Morganov commented Feb 14, 2021

Changes

  • The branch name should be monospaced if it is not a reference to the word.

But the remote still has a _master_ branch.
Other collaborators will continue to use the _master_ branch as the base of their work, until you make some further changes.
Your local `master` branch is gone, as it's replaced with the `main` branch.
The `main` branch is available on the remote but the `master` still also there.
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
The `main` branch is available on the remote but the `master` still also there.
The `main` branch is present on the remote.
However the old `master` branch is still present on the remote.

How about something like this?

Copy link
Member Author

Choose a reason for hiding this comment

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

OK, but comma after the "however". Updated.

@Morganov Morganov force-pushed the feature/update-branches-names branch from 9fb0d4c to 22e9208 Compare February 16, 2021 18:25
@ben
Copy link
Member

ben commented Feb 16, 2021

This looks great to me. @HonkingGoose are you good with it?

@HonkingGoose
Copy link
Contributor

@ben I'm good with this. 😄 Permission to merge! 🚀

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