Projects

A project belongs to an organisation. It lists the skills and prompts one codebase should have, and who works on it. Tie a repository to a project with deftro init, and deftro sync installs what the project lists.

Create a project

Owners and admins can create projects.

1. Open Projects.
2. Select New project under the organisation.
3. Enter a Name. A Slug is suggested; it is permanent, because install commands and deftro carry it. Add a description if you like.
4. Select Create project.

Add artifacts

On the project page, Add skill uploads a new one straight into the project. To add an existing one, use Scoped skills & prompts: choose an artifact of the organisation and select Attach. Anyone who can publish in the organisation can attach. Organisation-wide artifacts show here too, marked Organisation-wide.

Detach removes an artifact from the project; it needs an admin or the project lead.

Project members

The project's members list shows who is assigned. An admin or the project lead can add an organisation member, raise the role they hold on this project, or select Make lead. See Roles and permissions.

Project settings

Select Project settings on the project page. An admin or the project lead can rename it, change its description, and, if the organisation allows it, turn on Skip review for this project. Versions published while that is on are permanently marked unreviewed. You can also start Import from GitHub here.

Archiving

Admins can select Archive in Project settings. An archived project keeps what is attached and still installs, but accepts no new artifacts, versions or invitations. Unarchive opens it again. Use Show archived projects on the Projects page to find it.

This project is archived

Code: archived

You tried to push Context into a space that belongs to an archived project. Its Context is read-only until the project is unarchived. Ask an admin to unarchive it, or push to another space.