lyra
a56d97d13d
Sync GitHub / sync (push) Successful in 7s
Previously, when Gitea is installed with DISABLE_GIT_HOOKS=true (the default), every git-hook API call returned 403 and the script: - marked every repository as FAILED, and - never counted the hook step at all. This change detects the disabled state up front with a single probe against the first editable repo: - If hooks are disabled, it prints a clear notice, skips the pre-receive step for every repo (branch/tag protection still runs normally), and exits non-zero (2) so automation notices the run is partial. - A per-repo 403 on the hook step is isolated (HookNotWritable) so it no longer clobbers the whole repo into FAILED -- branch/tag still apply, and the hook reports 'SKIPPED (git hooks not writable)'. - Adds a Hooks skipped counter and distinguishes 'disabled' vs 'not writable' in the summary. - Fixes an UnboundLocalError on the 'no editable repos' path by initializing hooks_enabled before the probe. Verified end-to-end against a mock Gitea API for both scenarios (hooks disabled -> skip + exit 2; hooks enabled -> exact/stale/missing handled correctly, exit 0).
Shell Scipts
A collection of shell scripts that I like to have on my server,
the setup folder contains steps to quickly configure a new debian machine.
Many of the scripts use config.sh, which there is an example config for reference.
It can contain information like discord webhooks, drives to monitor storage usage, etc.
Most used scripts is the *-all.sh scripts, which are various git functions run across
a collection of locations. So you can be in a code folder containing multiple projects,
and run status-all.sh to get a concise summary of each codebase without having to go into each one.