Skip to content

Edit docs_version_1.md #3159

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.

Sign up for GitHub

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

Merged
sspencerwire merged 1 commit into from
Feb 21, 2026
+13 −7
Merged

Edit docs_version_1.md #3159

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
20 changes: 13 additions & 7 deletions docs/guides/contribute/docs_versions_1.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -39,13 +39,13 @@ Cloning the Rocky Linux repository moves a copy of the Rocky Linux documentation
git clone git@github.com:rocky-linux/documentation.git
```

2. Change into the `/documentation` directory:
1. Change into the `/documentation` directory:

```bash
cd documentation
```

3. Check the remote name:
1. Check the remote name:

```bash
git remote -v
Expand All @@ -60,7 +60,7 @@ Cloning the Rocky Linux repository moves a copy of the Rocky Linux documentation

You want this resource to be "upstream" rather than "origin".

4. Change the remote name
1. Change the remote name

```bash
git remote rename origin upstream
Expand All @@ -84,7 +84,7 @@ With the Rocky Linux remote added and properly named, you need to set your perso
git remote add origin git@github.com:[username]/documentation.git
```

2. Check your git remotes:
1. Check your git remotes:

```bash
git remote -v
Expand All @@ -107,13 +107,19 @@ With the Rocky Linux remote added and properly named, you need to set your perso
git pull upstream main && git push origin main
```

2. Check out one of the two older version branches:
1. Make your local clone aware of the branches that exist on the `upstream` with:

```bash
git fetch upstream
```

1. Check out one of the two older version branches:

```bash
git checkout rocky-8
```

!!! warning "This does not work if your clone was from your fork"
!!! warning "This does not work if your clone was from your fork."

This is why the cloning process is done from Rocky Linux instead of from your fork. Your fork will not be aware of the older branches. To get the message that follows, you *must* clone your local documentation repository from Rocky Linux.

Expand All @@ -132,7 +138,7 @@ With the Rocky Linux remote added and properly named, you need to set your perso

You will probably get a message that you can create a pull request from the push. You can ignore this. What has happened is that your fork now has a `rocky-8` branch.

3. Check out the remaining older branch. (`rocky-9`) and repeat the steps you just ran with that branch.
1. Check out the remaining older branch. (`rocky-9`) and repeat the steps you just ran with that branch.

Once completed, you will now have `main`, `rocky-8`, and `rocky-9` branches on your local fork and clone, and will be able to write documentation on any of those branches.

Expand Down