Projects
Delete a project
What deleting an Ulika project removes, the exact confirmation dialog, and the Vercel deploy hook and repository connector files you must clean up yourself.
Last updated
Deleting a project removes it from Ulika for good. There is no undo and no version to restore from. Your GitHub repository and your live website are not touched, but a few things Ulika added to them stay behind, and you remove those yourself. This page lists exactly what goes and what you must clean up.
Before you delete#
Only owners and admins can delete a project. For everyone else the Delete project button is disabled with "Only owners and admins can disconnect a repository or delete a project." See Roles.
Deleting is immediate. Everything in Ulika for this project is gone: every field, collection item, media record and version, including History.
Disconnecting the repository is a smaller step if you only want Ulika to stop reading your code. See Project settings.
Consider whether another teammate still needs the project. The dialog offers no export.
How to delete#
Open the project and choose Settings, then the Danger zone tab.
Next to Delete project, click the red Delete project button. The row explains: "Removes this project along with every field, collection item, media record and version. Your repository and your deployed site are untouched."
A dialog titled Delete project opens. Read it (see below).
Type the project's name exactly where it says "Type (project name) to confirm." Capitals matter, and spaces at the start or end are ignored.
The red Delete project button unlocks when the name matches. Click it.
You can also press Enter in the box once the name matches. Cancel closes the dialog without doing anything. The server re-checks the name; if it does not match you see "Type the project name exactly to confirm."
What the dialog says#
The dialog opens with "There is no undo, and no version to restore from. Ulika removes:" and lists:
The project "(your project's name)" in Ulika, with every field, collection item, media record and version.
The access variable Ulika added to your Vercel project (
ULIKA_BUILD_TOKEN, orULIKA_CONNECTOR_TOKEN), its deployment webhook and its preview-bypass secret, where Vercel lets Ulika remove them.Ulika's record of this site's connection. The history of earlier connection runs is kept, marked as detached.
Then it says "What you do yourself, afterwards:" and lists the cleanup below.
What you must clean up yourself#
The Vercel deploy hook#
Ulika cannot remove the deploy hook it created, because Vercel hides deploy hooks from Ulika's access. In the dialog:
In Vercel, delete the deploy hook named "Ulika (project id)" if it is there (Settings > Git > Deploy Hooks). Vercel hides hooks from Ulika, so it cannot remove it for you.
Steps:
Click Open Vercel in the dialog, or go to your Vercel dashboard.
Open the project that hosts your site.
Go to Settings, then Git, then Deploy Hooks.
Find the hook named Ulika followed by the project's id and delete it.
Why this matters: a deploy hook is a secret web address that starts a build. Leaving it behind is harmless to your site, but it is an address that can trigger a rebuild, so tidy it up.
The connector in your repository#
The connector is what Ulika added to your repository through a pull request. The dialog says:
Your repository (owner/name) and your live site are not touched. For a clean repository, delete the .ulika/ folder and ulika.config.json, and restore your original build command (the connector wrapped it).
Steps in your repository (use a normal commit or pull request, as with any change):
Delete the
.ulika/folder.Delete
ulika.config.json.Restore your original build command (for example in
package.json). The connector changed it so Ulika's build step runs around yours.Commit, push and let your host rebuild.
The dialog links to Open the repository when Ulika knows its address.
After you click Delete project#
A toast says "(your project) deleted".
A second dialog, titled "(your project) is deleted" with "Here is what is left for you to do, with the links.", shows "Ulika removed:" and the same lists, now with direct links. Click Done to return to the dashboard.
If Ulika could not remove something from Vercel (for example it could not reach Vercel), an extra line appears first in the "What you do yourself" list: "Still on Vercel, and Ulika could not remove it:" followed by what is left, with an Open Vercel link. Remove it there. Ulika keeps a record of what is left so that a later run can retry.
If the delete fails you see "Could not delete the project" with the reason, and nothing is removed. Failing to remove something on Vercel never blocks the delete itself.
Installing the same site again#
The name of a deleted project is free to use again. Ulika also clears the project's delivery state (earlier publishes, repository binding, tokens and connection record), so a fresh connection starts clean. Connection runs from before are kept in history and marked as detached, with a note that says "This project no longer exists. Run the connect command again to set it up afresh". See Connect from the dashboard and Connect with the CLI.
Summary of what stays and what goes#
| Item | Result of deleting |
|---|---|
| The project, its fields, collection items, media records and versions in Ulika | Removed |
| Ulika's access variable, webhook and preview-bypass secret on Vercel | Removed where Vercel allows it |
| Ulika's connection record | Removed (earlier connection runs are kept, marked detached) |
| The Vercel deploy hook "Ulika (project id)" | You delete it |
.ulika/ and ulika.config.json in your repository, and the wrapped build command | You remove them |
| Your repository | Untouched |
| Your live website | Untouched |
Was this page helpful?