librewolf/website
14
55
Fork
You've already forked website
39

WIP: Renaming master to main #126

Draft
eIKpaSrnMoKI wants to merge 2 commits from eIKpaSrnMoKI/website:main into master
pull from: eIKpaSrnMoKI/website:main
merge into: librewolf:master
librewolf:master
librewolf:rel
librewolf:webgl
librewolf:changelog
librewolf:astro
Contributor
Copy link

It doesn't work that way, does it?
I would like to see the main development branch for the website renamed from master to main.

It doesn't work that way, does it? I would like to see the main development branch for the website renamed from `master` to `main`.

This will probably break a bunch of stuff that expects the branch to be called master. (existing PRs, CI etc.)
Master is also not a uncommon name for this, so.. I would not do this at the moment, especially since it has no real benefit.

This will probably break a bunch of stuff that expects the branch to be called master. (existing PRs, CI etc.) Master is also not a uncommon name for this, so.. I would not do this at the moment, especially since it has no real benefit.
Author
Contributor
Copy link

Well, it seems quite easy for me in my fork repository. I can simply rename the development branch.
I disagree with your statement about benefit. For me it's about choosing a language that doesn't further discriminate and hurt people. And your project can make a clear statement about this. People want to contribute. And I think it's important that they feel seen and heard.

Well, it seems quite easy for me in my fork repository. I can simply rename the development branch. I disagree with your statement about benefit. For me it's about choosing a language that doesn't further discriminate and hurt people. And your project can make a clear statement about this. People want to contribute. And I think it's important that they feel seen and heard.
Author
Contributor
Copy link

As far as I can see, some of your repositories still use master and others already use main. For me, it would be a global concern to convert all repositories. It doesn't have to be main, and in any case it should no longer be called master.

As far as I can see, some of your repositories still use master and others already use main. For me, it would be a global concern to convert all repositories. It doesn't have to be main, and in any case it should no longer be called master.
This pull request is marked as a work in progress.
This branch is out-of-date with the base branch
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u main:eIKpaSrnMoKI-main
git switch eIKpaSrnMoKI-main

Merge

Merge the changes and update on Forgejo.

Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.

git switch master
git merge --no-ff eIKpaSrnMoKI-main
git switch eIKpaSrnMoKI-main
git rebase master
git switch master
git merge --ff-only eIKpaSrnMoKI-main
git switch eIKpaSrnMoKI-main
git rebase master
git switch master
git merge --no-ff eIKpaSrnMoKI-main
git switch master
git merge --squash eIKpaSrnMoKI-main
git switch master
git merge --ff-only eIKpaSrnMoKI-main
git switch master
git merge eIKpaSrnMoKI-main
git push origin master
Sign in to join this conversation.
No reviewers
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
librewolf/website!126
Reference in a new issue
librewolf/website
No description provided.
Delete branch "eIKpaSrnMoKI/website:main"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?