You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Following on from recent movements in other projects, I'd like to use more inclusive language in this project.
Namely:
A few instances of "whitelist" in the Security chapter for CSP. These are perfectly valid (it's in the CSP spec after all), but can easily be reworded to avoid this whole debate. Replace whitelist #883
Delete master branch after release and a period (2 weeks?), to avoid confusion.
Now I know some people have strong views as to the need, effectiveness and point of these sorts of changes, and I'm not wanting to get into the debate on whether or not these terms have anything to do with the negative connotations some might feel they have (whether intentional or not). However, I feel anything we can do to make people feel more inclusive is the right thing to do, and goes with the ethos of this project. Additionally these are very small changes for us and now is the right time to make these changes (before 2020 ramps up in earnest).
For the master -> main rename the following steps need to be done (this will keep all our commit history btw):
The default branch has been moved from master to main. Please follow above steps to update any local copies or forks. We will delete the master branch in a week or so.
Note if you want to just reset your forked main branch to be the same as the main repo, then you can do the following in your fork - after completing above steps:
git remote add upstream git@github.com:HTTPArchive/almanac.httparchive.org.git
git fetch upstream
git checkout main
git reset --hard upstream/main
git push origin main --force
Following on from recent movements in other projects, I'd like to use more inclusive language in this project.
Namely:
master
branch tomain
in Git. Master branch rename #881master
branch after release and a period (2 weeks?), to avoid confusion.Now I know some people have strong views as to the need, effectiveness and point of these sorts of changes, and I'm not wanting to get into the debate on whether or not these terms have anything to do with the negative connotations some might feel they have (whether intentional or not). However, I feel anything we can do to make people feel more inclusive is the right thing to do, and goes with the ethos of this project. Additionally these are very small changes for us and now is the right time to make these changes (before 2020 ramps up in earnest).
For the
master
->main
rename the following steps need to be done (this will keep all our commit history btw):git branch -m master main
git push -u origin main
main
branch as formaster
master
reference in GitHub actionmaster
branch after a period to avoid confusionLocal copies and forks can be updated with these commands:
Then change your own default branch in
/settings/branches
for your repo.Please comment if any technical concerns with this proposal or other suggested names rather than
main
.The text was updated successfully, but these errors were encountered: