This commit is contained in:
@@ -94,35 +94,6 @@ build/outputs/apk/debug/a3270-debug.apk
|
|||||||
|
|
||||||
---
|
---
|
||||||
|
|
||||||
## 🏷️ How to Tag & Publish (Beta) Releases
|
|
||||||
|
|
||||||
Releases can be published automatically to Gitea via Git tags:
|
|
||||||
|
|
||||||
```bash
|
|
||||||
# 1. Create a version tag (stable or beta)
|
|
||||||
git tag -a v0.1.0-beta.1 -m "Release v0.1.0-beta.1"
|
|
||||||
|
|
||||||
# Or a stable release:
|
|
||||||
git tag -a v0.1.0 -m "Release v0.1.0"
|
|
||||||
|
|
||||||
# 2. Push the tag to Gitea
|
|
||||||
git push origin v0.1.0-beta.1
|
|
||||||
```
|
|
||||||
|
|
||||||
Pushing any `v*` tag triggers the automated release workflow (`.gitea/workflows/release.yaml`), which:
|
|
||||||
1. Automatically detects pre-releases (tags containing `beta`, `alpha`, `rc`, `pre`, `preview`, or `dev`) and marks them as **Pre-release** on Gitea.
|
|
||||||
2. Builds the APK and packages it.
|
|
||||||
3. Publishes a new Gitea Release with `a3270.apk` attached automatically.
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## 🔍 Topics & Discoverability
|
|
||||||
|
|
||||||
Suggested keywords/topics for repository indexing:
|
|
||||||
`tn3270` · `tn3270e` · `ibm-3270` · `mainframe` · `terminal-emulator` · `android` · `android-app` · `jetpack-compose` · `kotlin` · `x3270` · `j3270` · `ind-file` · `file-transfer` · `ebcdic` · `z-vm` · `z-os` · `cms` · `tso` · `cics`
|
|
||||||
|
|
||||||
---
|
|
||||||
|
|
||||||
## 🤝 Contributing
|
## 🤝 Contributing
|
||||||
|
|
||||||
Contributions are welcome! Please feel free to open a bug report or feature request via the Gitea issue tracker.
|
Contributions are welcome! Please feel free to open a bug report or feature request via the Gitea issue tracker.
|
||||||
|
|||||||
Reference in New Issue
Block a user