# Project

**Help URL:** `/forms/project`

## Purpose

Create a new TestVibe project repository in GitHub, or edit/delete an existing project repository.

## Common Tasks

* Create a new private project repository from the TestVibe project template.
* Edit an existing project’s display name, homepage URL, and description.
* Delete a project repository.

## Key UI Elements

* Project name: Human-friendly display name; used to generate the GitHub repository name.
* Homepage URL: Used as the default site URL for tests/runs; validated and normalized to `https://…` when missing a scheme.
* Project description: Stored in GitHub; can be auto-filled from the homepage URL.
* Create/Save: Creates the repository (create mode) or updates repository settings (edit mode).
* Delete (edit mode): Deletes the GitHub repository after confirmation.

## Notes

* Repository name is generated from the project name (slugged and validated) and must be a valid GitHub repo name.
* When creating a project, TestVibe also initializes the repo by running a template-clone workflow (and applies the `test-automation` topic).
* If the description is empty and you enter a homepage URL, TestVibe may attempt to summarize the URL and fill the description (best-effort).
* “Regenerate token” in edit mode is informational: TestVibe uses per-run tokens for generations rather than a long-lived repository token.
* Next steps: create tests in [Test](/reference/forms/test.md) and start runs in [Run](/reference/forms/run.md).


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.testvibe.com/reference/forms/project.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.