docs/docs-fp-o

Fork 14

Use `main` for `prod` #19

New issue

Open

opened 2026-03-08 23:58:54 +00:00 by jflory7 · 5 comments

jflory7 commented

2026-03-08 23:58:54 +00:00

Owner

The git branch workflow is confusing and hides the most useful content in this repository in a non-default branch. Therefore, I proposing the following:

Delete the current main branch.
Rename prod to be the new main branch.
Delete the stg branch.
(later) Use Forgejo Actions to build live previews of the entire docs site inside of PRs, therefore eliminating the need for a staging branch.

This should make it easier for people to navigate this repository, find the things they need to find, and propose changes more easily.

The git branch workflow is confusing and hides the most useful content in this repository in a non-default branch. Therefore, I proposing the following: 1. Delete the current `main` branch. 2. Rename `prod` to be the new `main` branch. 3. Delete the `stg` branch. 4. (later) Use Forgejo Actions to build live previews of the entire docs site inside of PRs, therefore eliminating the need for a staging branch. This should make it easier for people to navigate this repository, find the things they need to find, and propose changes more easily.

👍 3

jflory7 added the

help wanted

label

2026-03-08 23:58:54 +00:00

pboy commented

2026-03-09 10:05:34 +00:00

Owner

I would support that. We should check if the README.md is the same or what is the newer one. And according to our rules, I guess we need a Licence file? Or does it only apply for GitLab repos?

And before we delete stg, we have to check which projects use it.

I would support that. We should check if the README.md is the same or what is the newer one. And according to our rules, I guess we need a Licence file? Or does it only apply for GitLab repos? And before we delete stg, we have to check which projects use it.

venefilyn commented

2026-03-19 18:27:13 +00:00

Member

Yes, it's actively confusing and tedious to manage. If we ever need staging we can handle that through actions, or simply use local builds if it's something we develop

👍 1

pbokoc referenced this issue from docs/tickets

2026-04-01 11:01:17 +00:00

Get rid of stg branches #22

pbokoc commented

2026-04-01 11:01:42 +00:00

Owner

+1.

I also opened a separate ticket for doing the same thing in all the other repos - docs/tickets#22.

+1. I also opened a separate ticket for doing the same thing in all the other repos - https://forge.fedoraproject.org/docs/tickets/issues/22.

jibecfed commented

2026-04-09 03:42:20 +00:00

Member

same comment as #20
For the record, this will break https://forge.fedoraproject.org/docs/translations-scripts
This is not blocking
Please ping me and @darknao once you proceed with the update

same comment as https://forge.fedoraproject.org/docs/docs-fp-o/issues/20 For the record, this will break https://forge.fedoraproject.org/docs/translations-scripts This is not blocking Please ping me and @darknao once you proceed with the update

👍 1

pbokoc added the

labels

2026-05-29 09:51:16 +00:00

pbokoc commented

2026-05-29 09:52:26 +00:00