Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Change from master to main #648

Merged

Conversation

Dynnammo
Copy link
Contributor

@Dynnammo Dynnammo commented Oct 29, 2022

This is a 🔦 documentation change.

Summary

In the documentation, there's a lot of references to old named branches master. This PR correct them by renaming them main. Noteworthy : I didnt' change any coding files (or if so, it was only things commented) in order not to break anything, but with review help I can also manage it if wanted.

Context

Fix #642

Copy link
Contributor

@andrewmcodes andrewmcodes left a comment

Choose a reason for hiding this comment

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

@Dynnammo this changes all look excellent to me. Thanks for doing this!

I didnt' change any coding files (or if so, it was only things commented) in order not to break anything, but with review help I can also manage it if wanted.

I'd be happy to review. Perhaps open a new PR so this one can be reserved for documentation & internal utilities?

@jaredcwhite
Copy link
Member

Thanks @Dynnammo!

@jaredcwhite jaredcwhite merged commit 785e63f into bridgetownrb:main Nov 23, 2022
@Dynnammo
Copy link
Contributor Author

Wow just woke up to read all this, it ain't much but it's honest work, happy to be reviewed by the two heroes of the Bridgetownconf 🤯 . I'm also working on this related issue concerning GitLab deployment, if you have some insights or could give any advice or redirect me to any documentation that might help : #643

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.

docs: switch from master to main when relevant in the documentation
3 participants