docs: make repo references mirror-neutral for Gitea readers
The README and CONTRIBUTING are mirrored to both Gitea branches, so GitHub-specific references now name the GitHub repository explicitly instead of saying 'this repository'. Co-authored-by: arena-agent <297053741+arena-agent@users.noreply.github.com>
This commit is contained in:
co-authored by
arena-agent
parent
ec43d631d4
commit
7b381d0387
+5
-5
@@ -4,7 +4,7 @@ First off, thank you for considering contributing to Sovran_SystemsOS! 🎉
|
||||
|
||||
## This GitHub Repo
|
||||
|
||||
This repository is the **development mirror** of Sovran_SystemsOS and serves as
|
||||
The GitHub repository is the **development mirror** of Sovran_SystemsOS and serves as
|
||||
its connection to the GitHub ecosystem. The **main, stable repository** is
|
||||
self-hosted on the project's Gitea instance at
|
||||
https://git.sovransystems.com/Sovran_Systems/Sovran_SystemsOS
|
||||
@@ -13,15 +13,15 @@ as the ethos of Sovran_SystemsOS is self-sovereignty.
|
||||
|
||||
The workflow is:
|
||||
|
||||
1. Development happens on the `staging-dev` branch on Gitea, which this GitHub
|
||||
1. Development happens on the `staging-dev` branch on Gitea, which the GitHub
|
||||
repository mirrors.
|
||||
2. All activity in this GitHub repo — issues, pull requests, reviews, and
|
||||
2. All activity in the GitHub repo — issues, pull requests, reviews, and
|
||||
testing — is done against the mirrored `staging-dev` code.
|
||||
3. When changes are complete and tested, they are moved to the `stable` branch
|
||||
on the Gitea instance, which is the code used by released Sovran_SystemsOS
|
||||
builds.
|
||||
|
||||
Please note: this repo mirrors `staging-dev`, so it may contain new features
|
||||
Please note: the GitHub repo mirrors `staging-dev`, so it may contain new features
|
||||
and code not yet in the `stable` branch on Gitea, and this code is not fully
|
||||
tested.
|
||||
|
||||
@@ -43,7 +43,7 @@ Moreover, Sovran_SystemsOS has been improved with the help of AI. We have used C
|
||||
### 🔧 Submitting Code Changes
|
||||
|
||||
#### 1. Fork the Repository
|
||||
Click the "Fork" button at the top right of this repository.
|
||||
Click the "Fork" button at the top right of the GitHub repository.
|
||||
|
||||
#### 2. Clone Your Fork
|
||||
```bash
|
||||
|
||||
Reference in New Issue
Block a user