Christoph/GitLite
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 35 Wiki Activity

feat(ci): automate arch package build and distribution
publish / Build and publish Arch package (release) Failing after 1s
Details
publish / publish-tauri (nsis, , windows-latest, windows-x86_64) (release) Canceled after 0s
Details
publish / publish-tauri (appimage, 1, ubuntu-22.04, linux-x86_64) (release) Canceled after 1m59s
Details

Browse Source 
The continuous integration pipeline is significantly enhanced to fully automate the process of building, packaging, and publishing Gitty as an Arch Linux repository. A new dedicated workflow job handles version setting, dependency resolution, and package creation using makepkg within a Docker container environment. This ensures that every release is properly packaged and uploaded to the configured MinIO/S3 location for system-wide distribution.

- Added `publish-arch` job to CI pipeline
- Implemented repository management logic in arch_repo.py
- Updated PKGBUILD with necessary desktop dependencies
This commit is contained in:
Christoph Brandau
2026-07-23 00:58:32 +02:00
parent 27c8b40dc6
commit 8220e36629
4 changed files with 177 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.md
+22
View File
@@ -52,6 +52,28 @@ MIT License
---
## Arch Linux
Release builds are published as an `x86_64` pacman repository. Add this block to
`/etc/pacman.conf` once:
```ini
[gitty]
SigLevel = Optional TrustAll
Server = https://cdn.cbsk-tech.de/gitty/arch/$arch
```
Then install Gitty and receive future releases through the normal system update:
```bash
sudo pacman -Syu gitty
```
The repository is currently distributed over HTTPS but is not GPG-signed. A
repository signing key should be added before recommending it to third parties.
---
## SigNoz telemetry
After the user opts in, Gitty sends privacy-filtered product events and technical errors as OTLP/HTTP JSON logs. Every Git/Tauri command is also captured as a trace span with its command name, duration and success state, but without command arguments or results. CPU utilization and resident memory usage of the Gitty process are sampled every 30 seconds and exported as OpenTelemetry gauges. The default endpoints are `https://telemetry.cbsk-tech.de/v1/logs`, `https://telemetry.cbsk-tech.de/v1/traces`, and `https://telemetry.cbsk-tech.de/v1/metrics`.