Skip to content

fix(ci): repair Flatpak gh-pages publish (was silently failing) + autostart doc#140

Merged
nvdweem merged 2 commits into
mainfrom
worktree-linux-auto-update
Jul 14, 2026
Merged

fix(ci): repair Flatpak gh-pages publish (was silently failing) + autostart doc#140
nvdweem merged 2 commits into
mainfrom
worktree-linux-auto-update

Conversation

@nvdweem

@nvdweem nvdweem commented Jul 14, 2026

Copy link
Copy Markdown
Owner

The Flatpak job was silently failing (masked by continue-on-error) so gh-pages was frozen at the first run — stale .flatpakref (the install 404) and bare landing page. Root cause: git drops OSTree’s empty dirs on the gh-pages round-trip, so ostree prune died on opendir(refs/remotes). Recreate those dirs; also make a Flatpak/Pages failure mark the job red instead of green.

Also: document Flatpak autostart in linux.md.

AI-generated; the fix is a direct response to the exact CI error. Verified end-to-end by the following build.

This pull request was made by an AI without any human intervention

🤖 Generated with Claude Code

https://claude.ai/code/session_01CjZYH14th2uGJAMPRRpbsf

Niels and others added 2 commits July 14, 2026 20:49
flatpak install can't enable autostart (the sandbox can't write the host
autostart dir), so give a dedicated Flatpak subsection: use the desktop's
autostart settings, or a host ~/.config/autostart/*.desktop with
'flatpak run com.getpcpanel.PCPanel quiet'.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01CjZYH14th2uGJAMPRRpbsf
The Flatpak job silently failed and never updated gh-pages: cloning the repo
back from the gh-pages branch drops OSTree's empty dirs (git doesn't store
empty directories), so 'ostree prune --refs-only' died with
'opendir(refs/remotes): No such file or directory'. Because the build step was
continue-on-error, the job showed green and the publish step was skipped by its
outcome=='success' guard — so gh-pages stayed frozen at the first run (stale
.flatpakref, bare landing page).

- Recreate site/repo/refs/{heads,remotes,mirrors} and tmp after cloning.
- Make failures visible: give the publish step an id and add a final step that
  marks the JOB red when the build or publish fails. Job-level continue-on-error
  still keeps the release unblocked (.deb + AppImage ship regardless).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01CjZYH14th2uGJAMPRRpbsf
@nvdweem
nvdweem merged commit 8cf1ebc into main Jul 14, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant