Skip to content

Point the fork workflows at main after the branch rename - #106

Merged
float3 merged 3 commits into
mainfrom
fix-main-ci
Nov 4, 2026
Merged

float3 merged 3 commits into
mainfrom
fix-main-ci

Conversation

@float3

@float3 float3 commented Nov 4, 2026

Copy link
Copy Markdown
Owner

The default branch was renamed from ankiquest to main after #93, but the ankiquest_* workflows still pointed at ankiquest:

  • Sync upstream AnkiDroid (scheduled, 2026-11-02 and 11-03) and ankiquest flake.lock update (2026-11-02) failed at checkout with "A branch or tag with the name 'ankiquest' could not be found". Both now check out main and open their PRs into main. The sync job finds an open ankidroid:main → main PR such as sync #104 and leaves it alone. nix flake update itself works (tried on NixOS: it bumps nixpkgs 2026-10-27 → 2026-11-01) and so does nix flake check.
  • On pushes to main, ankiquest APK (so no nightly release), ankiquest Code Quality Checks, ankiquest Emulator Tests, ankiquest Nix, ankiquest shared fixtures and ankiquest signing key rotation never ran, and the fixtures check also skipped PRs into main. Their branches: filters and the nightly refs/heads/ankiquest check now say main. ankiquest Unit Tests gets the same change in Run fork PR unit tests on ubuntu only #105, so it isn't touched here.
  • ankiquest Screenshots: Store Baseline drops ankiquest, and the workflow regression tests stop asking for an ankiquest baseline.
  • The README badges and licence link pointed at the old branch.

The sync job also tries the upstream merge before it opens or reuses the PR. Conflicting files go into a warning and the job summary, so the run says what to resolve in the merge branch (it currently lists gradle/libs.versions.toml). A conflict doesn't fail the job, because a daily red run would only repeat what the PR already shows.

ankiquest Emulator Tests still had upstream's "don't run scheduled jobs on forks" guard, so its weekly Monday run skipped itself every time (2026-11-02). That guard is gone; this is the same change #105 makes for unit tests.

Other failures on main, nothing to change

  • 🛠️ Unit Tests on bd32faa: the macOS job was cancelled because no runner was acquired ("The job was not acquired by Runner of type hosted even after multiple attempts"). Ubuntu and Windows passed, so there's no test failure. This is upstream's tests_unit.yml, which should be disabled as Keep fork CI in ankiquest_* workflows, restore upstream .github #88 lists.
  • ankiquest Screenshots: Compare on bd32faa: no baseline existed for main yet, because it was the first push to the renamed branch and Store Baseline ran at the same time. That Store run succeeded (run 41427799883, artifact kept until 2026-12-02), and later compares find it (Run fork PR unit tests on ubuntu only #105's compare passed). Rerun that compare if you want main green. It fails on a missing baseline on purpose (see .github/tests/screenshots.test.cjs).

actionlint is clean apart from existing shellcheck info notes, and node --test .github/tests/*.test.cjs passes.

The default branch moved from ankiquest to main, but the ankiquest_*
workflows still named ankiquest. The upstream sync and flake.lock jobs
failed checking out a branch that no longer exists, and pushes to main
skipped the APK (so no nightly), lint, emulator, nix, fixtures and
signing checks.

The sync job now also tries the upstream merge and lists conflicting
files in a warning and the job summary. The scheduled emulator run no
longer skips itself on forks, so the weekly run happens here.
@github-actions

github-actions Bot commented Nov 4, 2026 •

Copy link
Copy Markdown

Snapshot diff report: Previous regressions were resolved by the latest commit.

# Conflicts:
#	.github/workflows/ankiquest_tests_unit.yml
@float3
float3 merged commit 2b0fa6d into main Nov 4, 2026
40 of 41 checks passed
@float3
float3 deleted the fix-main-ci branch November 4, 2026 15:27
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