When the Steward isn't working as it should

First, look at what it says#

The Steward says why it does what it does. Look at:

• Needs you, at the top of its page, and in Castellan;
• the pull request's row under Your repositories, which says what holds it;
• Last stage, with the log of the last round or button.

A pull request isn't merged#

Go down this list:

1. Merging is off for its repository. The row's badge says PRs left to you. Turn on The Steward merges ready pull requests for it in Castellan's Settings > Repositories.
2. The rounds don't merge. Merges and releases by itself is off in the Steward's settings (as it is on a new install), or the Steward is off duty. Use Merge your ready PRs, or turn it on.
3. It's a draft. Mark it ready on GitHub.
4. It isn't your team's. The Steward merges only pull requests from the accounts under Team, or from the account gh is signed in as when that's empty.
5. Its checks are failing or still running, or it doesn't merge cleanly. A conflict that's only in version lines or the changelog is caught up for you; any other is sent back to you in a comment.
6. It goes into another branch than the repository's (its row shows into that branch).
7. Its version isn't new: already released, not above the branch's, or another pull request's or claim's. Claim one with claim-version, set it, and push. See Versions claimed up front.
8. GitHub runs no checks, and the repository has no Tests command, so it can't be tested here. Add one in Castellan's Settings > Repositories, or vouch for it.
9. Another PC has the repository's turn. Its row says so. See The Steward on several PCs.

Tests fail here but pass for you#

The Steward tests a pull request in a fresh worktree at its head commit, with nothing from your clone: no uncommitted files, no local .env, packages installed from the lockfile.

• Run them as it does: commit and push everything, then run the tests in a fresh clone, or git worktree add one at the pull request's head.
• A test that depends on time or load can fail when several repositories are tested at once. A failure is tried once more at once; lower Checked at once in its settings if it keeps happening.
• Vouch for it once the tests pass in your clone, and it isn't tested here again: Vouching, and pull requests the Steward opens.

A release failed#

The alarm says what the release said. The rounds don't try it again at that commit.

• gh isn't signed in, or its account can't create releases in the repository: run gh auth login.
• The repository's release command failed: run it yourself in a clean clone of the branch to see why.
• The release command finished without making the GitHub release v<version>: it must make that release itself. Or set Release to tag and let the Steward make it.

Once it's fixed, choose Release on the Steward's page, or push a new commit: the next round tries that.

The rounds can't run#

Usually gh: "gh isn't installed" (install the GitHub CLI), or it isn't signed in (gh auth login). After an hour it's an alarm.

A repository isn't offered under Found on this PC#

Found on this PC offers only repositories that:

• Reeve found here (see Your repositories in Reeve: add its folder there, or stop leaving it alone);
• have an origin on GitHub;
• the account gh is signed in as can push to;
• aren't looked after already, and aren't one of Castellan's own.

The list is kept for an hour: Look again looks now. Or add the repository yourself in Castellan's Settings > Repositories, with its Repository as owner/name.

Vouch or claim-version refuses#

Each says why, in a sentence. See When vouch refuses. claim-version answers "No repository … here" when the name isn't a repository it looks after, one Reeve found here, or the clone it's run in: run it from the clone, or use the repository's owner/name.

Another PC merges or releases it#

That PC has the repository's turn. Do it here, on its row, takes it for this PC; Keep it on this PC keeps it here. See The Steward on several PCs.

An update was rolled back#

The new version didn't start properly, so the old one was put back, and the alarm says what failed. A newer version installs as usual. To try that version again, Dismiss the alarm. See An update that was rolled back.

The Steward's page won't open#

Its page is http://steward.localhost:19494/. Open on its card in Castellan starts it if it's down. It starts at sign-in from the scheduled task \Steward\Home page. If that doesn't help, run Castellan's setup again, with Install again what's installed already ticked. See Install Castellan.

Still stuck?#

Write to us at support@castellan-software.com with the Steward's version (on its card in Castellan), what you expected, and what its page or Last stage said. Look over any log before you send it, as it holds paths and repository names from your PC.