README.md aktualisiert
build-elsword-ge / build (push) Has been cancelled

This commit is contained in:
2026-06-27 17:42:43 +02:00
parent aa7efaa572
commit 7f44ea0fae
-66
View File
@@ -211,72 +211,6 @@ For Proton logs:
PROTON_LOG=1 %command%
```
## Gitea Actions behavior
Workflow file:
- [.gitea/workflows/build.yml](/home/magges/git/Elsword-GE/.gitea/workflows/build.yml:1)
Behavior:
- Push to `main`: builds both variants and stores build artifacts.
- Tag matching `v*`: builds both variants, packages them, generates checksums, and creates or updates a Gitea release with uploaded assets.
Expected secrets:
- `GITEA_TOKEN`
- `GITEA_SERVER_URL`
- `GITEA_REPOSITORY`
No tokens or passwords are stored in the repository.
## Manual fallback if release upload needs to be done by hand
If your Gitea release upload path differs or the API step needs adjustment for your instance, build locally or through Actions and upload these files manually in the release UI:
- `dist/Elsword-GE-11-1.tar.zst`
- `dist/Elsword-GE-11-1+dxvk-git.tar.zst`
- `dist/Elsword-GE-11-1-dxvk-git.tar.zst`
- `dist/SHA256SUMS.txt`
- `dist/*.sha256`
- `dist/release-notes.md`
## Push to Gitea
```bash
git init
git add .
git commit -m "Initial Elsword-GE build project"
git remote add origin ssh://git@DEIN-GITEA-SERVER/USER/elsword-ge.git
git push -u origin main
```
## Create a release by tag
```bash
git tag v11-1
git push origin v11-1
```
## Gitea attachment size note
Built Proton archives are usually much larger than 50 MB. Your Gitea instance may need larger release attachment limits.
Example configuration hint only; exact keys can vary by Gitea version:
```ini
[repository.upload]
FILE_MAX_SIZE = 2048
MAX_FILES = 20
[attachment]
MAX_SIZE = 2048
MAX_FILES = 20
[actions]
ENABLED = true
```
## Security and anti-cheat note
This project intentionally avoids: