Publish the project website on fdroid-repo (the branch Pages serves) - #654
Closed
BrawlerXull wants to merge 3 commits into
Closed
Publish the project website on fdroid-repo (the branch Pages serves)#654BrawlerXull wants to merge 3 commits into
BrawlerXull wants to merge 3 commits into
Conversation
Copy link
Copy Markdown
Collaborator
Sorry, something went wrong.
Pages for this repository is configured as branch-based, serving `fdroid-repo` at the root, so that is the only branch whose contents actually appear at https://ccextractor.github.io/taskwarrior-flutter/. The site lived on a feature branch where nothing could serve it; this puts the built output where Pages will. Only additions — every existing path is untouched, so the F-Droid repo, its metadata, assets and index are exactly as they were. The site occupies the root and `repo/` continues to serve F-Droid clients. Two deliberate choices: - Built for https://ccextractor.github.io/taskwarrior-flutter/ rather than the custom domain, because no custom domain is configured on Pages right now. - The generated CNAME (taskwarrior.ccextractor.org) is NOT included. Committing it would make Pages claim a domain with no DNS pointing at it, which would take the site offline and, worse, break the F-Droid repo URL that existing users' clients already poll. Once the DNS record exists, add the CNAME and rebuild with that baseURL. - .nojekyll added so Pages serves the files as-is instead of running them through Jekyll on every push. The nightly F-Droid workflow force-pushes this branch, but it checks out fdroid-repo before building its orphan commit and then `git add .`, so the site files are re-added and survive the deploy. That does mean the site depends on that checkout step continuing to exist. Hugo source stays with the app code; only the built output belongs here.
Copy link
Copy Markdown
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command. ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: a5b40dc5-6390-4f45-a5c8-9ae722e2cd3d You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file. Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. ❤️ ShareComment @coderabbitai help to get the list of available commands. |
Sorry, something went wrong.
…ined The built output already lived here; the source that generates it stayed with the app. That split meant the site could not be rebuilt from the branch that serves it, and the app repository carried 19 files it never compiles or ships. Both halves now live together: website/ (content, layouts, static, hugo.toml, data) and scripts/update_build_log.py, which records each deploy into website/data/nightly_builds.json for the Downloads table. update_build_log.py now takes the commit sha and subject as arguments. It used to read git HEAD, which is wrong here: the deploy switches the work tree to this branch before recording, and at that point HEAD is this branch's own orphan commit rather than the app commit being released. Omitting the arguments still falls back to git, so running it by hand is unchanged. Verified: Hugo builds all 15 pages from this branch alone, and nothing in the branch's .gitignore (which excludes /android, /ios, /build and friends) swallows any of the added files.
SGI-CAPP-AT2
pushed a commit
that referenced
this pull request
Aug 23, 2026
Last night's deploy (run 32580483451) died at "Record deploy and rebuild the website": the step assumes website/ and scripts/update_build_log.py are on the deploy branch, but the PR that puts them there (#654) has not been merged yet, so the checkout brought neither and python3 exited 2. Because the step sits between `fdroid update` and the push, the failure cancelled "Push F-Droid updates" — a website problem blocked the APK deploy, the one thing this workflow exists to do. No harm to clients: the force-push never ran, so fdroid-repo still serves the previous good deploy; the nightly was simply skipped. Two changes: - the website step now checks that the site source is actually on the deploy branch and skips with a workflow warning when it is not. Absence is a known transitional state (the website PR unmerged, or rolled back), not a build failure. When the source IS present, any failure remains fatal so real site breakage stays loud instead of half-noticed - workflow_dispatch, so a missed deploy can be redone by hand — until now the only trigger was a push to main, making an otherwise-pointless commit the only way to recover a skipped nightly Verified: yaml parses; the guard condition mirrors exactly the two paths the step uses (scripts/update_build_log.py, website/).
github-actions
Bot
force-pushed
the
fdroid-repo
branch
from
edb8805 to
fd2b85a
Compare
August 23, 2026 07:48
BrawlerXull
added a commit
to BrawlerXull/taskwarrior
that referenced
this pull request
Aug 23, 2026
Recreation of CCExtractor#654 on the current branch root. The original was auto-closed by github-actions[bot] the moment the deploy workflow force-pushed this branch: each deploy replaces the branch with a fresh orphan commit, so a PR based on the previous root loses its merge base and GitHub closes it. The 37 site files (website/ Hugo source, scripts/update_build_log.py, the prebuilt site at the root so Pages serves it immediately) are unchanged from CCExtractor#654. One addition beyond CCExtractor#654: /rust in .gitignore. The deploy runner compiles the Rust FFI before switching to this branch; rust/target/ survives the switch as untracked files — main's gitignore covers it, this one predates the Rust pipeline and did not — and the 2026-08-23 deploy's "git add ." swept 4318 build artifacts into the published branch. No secrets were exposed (android/, config.yml and keystore.p12 were already ignored). The junk is not deleted here: the next deploy rebuilds the branch from scratch and, with the ignore line in place, purges it automatically.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why this targets fdroid-repo
GitHub Pages for this repository is branch-based, serving fdroid-repo at the root:
build_type: legacy source: { branch: fdroid-repo, path: / } url: https://ccextractor.github.io/taskwarrior-flutter/So fdroid-repo is the only branch whose contents actually appear at that URL. The site (D5) was built on a feature branch where nothing could serve it — this puts the built output where Pages will pick it up.
What this changes
Additions only — 17 files, no existing path modified. The F-Droid repo, its metadata, assets and index are unchanged. The site occupies the branch root; repo/ continues to serve F-Droid clients exactly as before.
Two deliberate choices
Built for https://ccextractor.github.io/taskwarrior-flutter/, not the custom domain — because no custom domain is configured on Pages at the moment.
The generated CNAME (taskwarrior.ccextractor.org) is deliberately excluded. Committing it would make Pages claim a domain with no DNS pointing at it. That would take the site offline and — more seriously — break the F-Droid repo URL that existing users' clients already poll. Once the DNS record exists, add the CNAME and rebuild with that baseURL.
.nojekyll is included so Pages serves the files as-is rather than running Jekyll on every push.
Interaction with the nightly deploy
nightlydepolyci.yml force-pushes this branch. It is safe: the workflow does git checkout fdroid-repo before building its orphan commit and then git add ., so these files are re-added and survive each deploy. Worth knowing the site therefore depends on that checkout step continuing to exist — if the workflow is ever changed to a clean checkout, the site would be dropped.
Note
Only the built output belongs here; the Hugo source stays with the app code.