[fedora-websites] Issue #1117: Update README.md
by Ojong Enow
d-enow reported a new issue against the project: `fedora-websites` that you are following:
``
The README.md file can be updated to include details that would make it easier for new contributors to get started such as how to submit a first pull request.
Also, the setup procedure is slightly different for other Unix-based distros like Debian. This can be included too for non-fedora users.
``
To reply, visit the link below or just reply to this email
https://pagure.io/fedora-websites/issue/1117
1 year, 3 months
[fedora-websites] Issue #1123: Change default branch to main
by Justin W. Flory
jflory7 reported a new issue against the project: `fedora-websites` that you are following:
``
# Summary
Change default Pagure git branch from `master` to `main` and recreate `master` as a branch alias
# Background
Fedora Linux 34 [switched default git branches to `main`](https://fedoraproject.org/wiki/Changes/GitRepos-master-to-main) as a Self-Contained Change. Many repositories use `main` as the default branch. In addition to being courteous, kind, and respectful, there are a few places that mention this branch to use `main` already, so we should take some form of action with the [Pagure git branch aliases](https://docs.pagure.org/pagure/changelog.html#id5).
# Details
1. Create a new main branch checked out from master
1. Change Pagure default branch to main
1. Delete master branch
1. Recreate master branch as a Pagure branch alias to main
The only risk to this change is what the impact will be to all opened Pull Requests. In `#websites:fedora.im`, we were thinking to work through the backlog of Pull Requests first in order to make this change safely.
# Outcome
* Syncs up with other distro-wide efforts to change default branches
* Use git branch aliases to allow both `master` and `main` to serve the same content
``
To reply, visit the link below or just reply to this email
https://pagure.io/fedora-websites/issue/1123
1 year, 4 months