Skip to content
Sengi

Renamed and moved repositories no longer stall jobs

What changed?

A repository that is renamed, recreated under its old name, or moved to another GitHub installation in the same Sengi project is now matched correctly. A repository that still conflicts is set aside on its own and the rest of the installation keeps running.

Details

Sengi now applies an installation's repository list as one complete update, with renames applied before name checks. A repository moved to another installation in the same Sengi project is transferred: its old record keeps its jobs and billing history, and the receiving installation records the repository again with new consent and an empty cache.

A repository whose name or identity is held by another project is never claimed. It is set aside and logged by itself, where before it could hold the whole installation. If a repository still does not receive jobs after a rename or move, see the troubleshooting page.

More changes

Keep your workflow. Cut your runner rate.

Sengi Basic starts at $0.001 a minute for 2 vCPU. Choose 4 or 8 vCPU for $0.002 or $0.004 a minute. Premium stays optional at $0.003, $0.006 and $0.012.

Start without a card ↗︎

See Basic pricing · Switch with your coding agent