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

Update references of hard-coded legacy master branch name to main branch name #67

Open
kelynch opened this issue Jun 30, 2021 · 2 comments
Assignees
Labels

Comments

@kelynch
Copy link
Contributor

kelynch commented Jun 30, 2021

Descriptive summary

This repository’s default branch has already been renamed using GitHub’s renaming tool. Links that reference the old branch name are automatically forwarded to the new default branch. But string references are not automatically updated.

Check this repository for hard-coded string references to the legacy “master” default branch and update them to the new default branch name “main.”

Important places to check include, but are not limited to:

  • READMEs
  • wikis
  • other documentation

NOTE: READMEs, wikis, and other documentation are important to update to avoid confusion and correct errors in long lasting documentation.

Less common places to check:

  • code
  • Issues/PRs

NOTE: String references to themaster branch in Issues, PRs, and code are uncommon. Also Issues and PRs are temporal in nature, making it less critical to update those occurrences.

Rationale

Git's default "master" branch derives from "master/slave" jargon which perpetuates systemic racist language and systems (see email Replacing "master" reference in git branch names). To uphold our Code of Conduct, we must move away from the term "master" in our technical language (as well as words like blacklist or whitelist).

Related work

@jrgriffiniii jrgriffiniii self-assigned this Sep 22, 2022
@jrgriffiniii jrgriffiniii moved this from In Progress to Backlog in Samvera Component Maintenance Dec 12, 2022
@jrgriffiniii jrgriffiniii moved this from Backlog to Ready in Samvera Component Maintenance Dec 12, 2022
@jrgriffiniii jrgriffiniii removed their assignment Dec 12, 2022
@jrgriffiniii jrgriffiniii moved this from Ready to Backlog in Samvera Component Maintenance Dec 12, 2022
@jrgriffiniii jrgriffiniii self-assigned this Dec 12, 2022
@jrgriffiniii jrgriffiniii moved this from Backlog to In Progress in Samvera Component Maintenance Dec 12, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: In Progress
Development

No branches or pull requests

2 participants