CI: Add README.md and CODEOWNERS
All checks were successful
ci/woodpecker/push/woodpecker Pipeline was successful
All checks were successful
ci/woodpecker/push/woodpecker Pipeline was successful
This commit is contained in:
3
.gitea/CODEOWNERS
Normal file
3
.gitea/CODEOWNERS
Normal file
@@ -0,0 +1,3 @@
|
|||||||
|
.woodpecker.{yml,yaml} @https/CI
|
||||||
|
.gitea/CODEOWNERS @https/CI
|
||||||
|
README.md @https/CI
|
||||||
21
README.md
Normal file
21
README.md
Normal file
@@ -0,0 +1,21 @@
|
|||||||
|
# Contributing
|
||||||
|
|
||||||
|
## Branch Protection
|
||||||
|
- **`main` branch is protected** — direct pushes are disabled.
|
||||||
|
- All changes must go through **Merge Requests (MRs)**.
|
||||||
|
- MRs require approval from code owners before merging.
|
||||||
|
|
||||||
|
## CI/CD
|
||||||
|
- Deployment is automated via **Woodpecker CI**.
|
||||||
|
- Pipeline triggers on every push to `main` after merge.
|
||||||
|
- Configuration: `.woodpecker.yml`
|
||||||
|
|
||||||
|
## Workflow
|
||||||
|
1. Create a feature branch from `main`
|
||||||
|
2. Make changes and push (put web content in `/public`)
|
||||||
|
3. Open a Merge Request
|
||||||
|
4. Wait for CI checks + code owner review
|
||||||
|
5. Merge when approved
|
||||||
|
|
||||||
|
## Code Owners
|
||||||
|
See `.gitea/CODEOWNERS` for responsible maintainers.
|
||||||
Reference in New Issue
Block a user