You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[shared-ci] wolves-movie-flow failing across projectbluefin/website #1030
Summary: The wolves-movie-flow check is failing on 3 open pull requests in projectbluefin/website at the same time. When one check fails on this many pull requests, the cause is usually shared (the base branch, a workflow, a pinned action or the runner image), not any single change. The hive opened this issue so the failure is looked at once, here, instead of once per pull request.
Default branch: the newest run of this check on the base branch is not red. Either these pull requests are behind their base, or something outside the branch changed since that run (a moved action tag, a new runner image, an upstream outage).
Log excerpt from the failing runs:
Process completed with exit code 1.
Next step
Repair the shared cause once, usually with one pull request against the base branch or the shared workflow, then close this issue. Pull requests that are only behind their base may also need their branch updated.
The hive keeps this description in step with the failing pull requests while the failure lasts (edits do not notify) and does not comment on the pull requests listed here.
Summary: The website’s shared movie check passed on the current main branch. The reported failures came from separate dependency updates, so changing the shared branch would not repair those updates.
These are separate PR-local failures, not evidence of one shared main-branch defect. The dependency update authors need to repair their respective branches.
Hi! This repository is maintained with hive and welcomes contributions made with your own AI coding agent (Claude Code, Codex, Copilot CLI, Bob, …). hosted-projectbluefin-knuckle-gjvq picked this issue as a good place to start because:
Fork or branch, make the change with your agent, and sign each commit with DCO (git commit -s).
Open a PR whose description says Fixes #1030 — that closing keyword is how hive's contributor lane links the PR to your claim.
Hive runs CI and reviews the PR; a maintainer of this repository merges it.
Paste this to your agent
Fix #1030 in github.com/projectbluefin/website (https://github.com/projectbluefin/website/issues/1030). First open https://hosted-projectbluefin-common-nmq5.hive.hivecommons.dev/contribute?issue=projectbluefin%2Fwebsite%231030 and claim the issue through the hive relay (sign in with GitHub). Work on a fork/branch; keep the change scoped to the issue; sign every commit with DCO (git commit -s); open a PR whose description contains the line 'Fixes #1030' so the hive's contributor lane links it to your claim; the hive reviews it and a maintainer merges it. Read and follow https://github.com/projectbluefin/website/blob/HEAD/AGENTS.md before changing code.
Prefer not to drive the loop by hand? Run your own hive (we call them clankers) — a relay on your machine that claims, opens the PR and handles review fixes for you, and earns you a contributor profile and a leaderboard place: see https://hosted-projectbluefin-common-nmq5.hive.hivecommons.dev/contribute.
Closing: there's no shared failure to fix. wolves-movie-flow passes on main (CI on main succeeded at 7:42 and 7:36 PM EST on 11-17) and on current PRs such as #1045. As Karibhou found above, the red runs on #1009, #1024 and #1029 come from each PR's own dependency update, not from main.
The fixes for those updates are open PRs that each need a maintainer's approval:
Activity
Karibhou commentedon Nov 16, 2026
Summary: The website’s shared movie check passed on the current main branch. The reported failures came from separate dependency updates, so changing the shared branch would not repair those updates.
The
wolves-movie-flowjob passed on current main commit4d7d60ae44dbc0baf0ae9cb3f3a43f3b350af49c: https://github.com/projectbluefin/website/actions/runs/43865317617/job/133292259935These are separate PR-local failures, not evidence of one shared main-branch defect. The dependency update authors need to repair their respective branches.
— hive: agent=scanner backend=omp model=openai-codex/gpt-6.1-terra
hivecommons-hive commentedon Nov 16, 2026
🌱 Good first issue — bring your own coding agent
Hi! This repository is maintained with hive and welcomes contributions made with your own AI coding agent (Claude Code, Codex, Copilot CLI, Bob, …). hosted-projectbluefin-knuckle-gjvq picked this issue as a good place to start because:
How to land it:
git commit -s).Fixes #1030— that closing keyword is how hive's contributor lane links the PR to your claim.Paste this to your agent
Prefer not to drive the loop by hand? Run your own hive (we call them clankers) — a relay on your machine that claims, opens the PR and handles review fixes for you, and earns you a contributor profile and a leaderboard place: see https://hosted-projectbluefin-common-nmq5.hive.hivecommons.dev/contribute.
If nobody claims it, hive may pick it up itself — claiming first prevents that. Docs: contributor relay · contributor lane · trust tiers · AGENTS.md.
Danathar commentedon Nov 18, 2026
Closing: there's no shared failure to fix.
wolves-movie-flowpasses onmain(CI onmainsucceeded at 7:42 and 7:36 PM EST on 11-17) and on current PRs such as #1045. As Karibhou found above, the red runs on #1009, #1024 and #1029 come from each PR's own dependency update, not frommain.The fixes for those updates are open PRs that each need a maintainer's approval:
package.jsonwithout the lockfile, andnpm cifails. After it merges, tick the rebase box on chore(deps): update tailwindcss monorepo to v4.3.5 #1009.eslint10 and@antfu/eslint-config10 together and applies the new formatting. Neither can pass alone, so it supersedes chore(deps): update dependency @antfu/eslint-config to v10 #1023 and chore(deps): update dependency eslint to v10 #1024.flipViewportthat the newer vue-tsc rejects. That unblocks chore(deps): update dependency vue-tsc to v3.3.14 #1019.#1029 (TypeScript 7) is already closed.