Skip to content
Sengi

Fix for jobs stuck after a deleted repo's name is reused

What changed?

Deleting a repository and creating a new one with the same name could stop Sengi runners for every repository on that GitHub installation. Sengi now releases the old name so the new repository is set up and its jobs run.

Details

Before this fix, the next check of the installation was held on a name conflict. While held, the installation was treated as inactive, so jobs for any repository on it were refused and waited in the queue, and the new repository was not set up.

The removed repository keeps its history, billing records and runner pages. In the API its name may show a suffix that marks it as removed. No action is needed.

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