ph project
Projects of the current organization: list, show, create, edit, delete
This page is generated from
ph project --helpbynpm run geninsite/, so do not edit it by hand.
text
Usage: ph project <command> (projects of the current organization)list
text
list [--json] Projectsshow
text
show <key> [--json] One project: name, repos, who created itimport
text
import [--all] [--repo owner/repo]... [--into <key>] [--json]
Create projects from the repositories you connected (GitHub App, GitLab group) that are not in a
project yet: one project per repository, key from the repository name (lowercase letters, digits,
dashes; a number is added when taken). --into puts all selected repositories in one project.
With no flag in a terminal it shows the list to choose from; without a terminal it needs --all or --repocreate
text
create <key> [--name <name>] [--repo owner/repo]... [--json]
Create a project (member or above; you become its project admin). The key is lowercase
letters, digits and dashes (shop-web); --name defaults to the keyedit
text
edit <key> [--name <name>] [--repo owner/repo]... [--add-repo owner/repo]... [--remove-repo owner/repo]...
Edit a project (project admin, or organization owner or admin). --repo replaces the whole listdelete
text
delete <key> [--yes] Delete a projectrelease-approvers
text
release-approvers <key> [list] [--json] Who can approve releases of the project in Bandum (besides organization owners). Empty: owners and admins onlyrelease-approvers (2)
text
release-approvers <key> set <login...> Replace the list (organization owner or admin; every login must be a member of the organization). With a
list, an admin who is not on it cannot approve; owners always canrelease-approvers (3)
text
release-approvers <key> clear Remove the list (back to owners and admins)visibility
text
visibility <key> private|org [--json] Who sees the project: org (everyone in the organization, default) or private (organization
owners, admins and the project's members). Organization owner or adminmembers
text
members <key> [list] [--json] Members of a private project, including its project admins (anyone who can see the project can read
the list)members (2)
text
members <key> set [<login>...] Replace the regular members (organization owner or admin; every login must be a member of the organization).
With no login they are all removed. Project admins always stay on the list and are never removed here.
Needs the private-projects feature (Team and Enterprise)members (3)
text
members <key> add <login> Add one login (read the list, then replace it)members (4)
text
members <key> remove <login> Remove one login (a project admin stays: it cannot be removed here)tracker
text
tracker <key> [show] [--json] Task source of the project: scm (issues) or a tracker kit such as Jira. Never prints a tokentracker (2)
text
tracker <key> set --kit kit-tracker-jira@1.1.0 --base-url <url> --project <KEY> [--email <e>] [--api-version 3|2] [--board-id <id>]
[--status-map "In QA=review;UAT Passed=approved"] [--level-field <id>] [--write-mode full|comment-only] [--token-stdin [--verify]]
Set the task source (organization owner or admin). The token is read from stdin only (never from
arguments); without --token-stdin Tara keeps the old token. --verify installs the kit, calls
me() with the token and stops before sending anything to Tara if that failstracker (3)
text
tracker <key> clear Back to scm and delete the stored tokenadoption
text
adoption <key> [--set YYYY-MM-DD | --reset] [--weeks <n>] [--json]
The date the project started using AI, the baseline for the before and after comparison
(ph insights flow --compare). Default: the earlier of the first day Ryoma received telemetry for the
project's repos and the day the project was created. --set (organization owner or admin) overrides it; --reset goes back to the defaultThis folder and Guardrails
use
text
use <key> [--no-verify] [--json] Bind this folder to a project: writes .phillip/project.json (commit it, so the whole team uses the
same project). Phillip sends the key to Tara (?project=<key>) to load the project-tier Guardrails policy.
Checks that the project exists in the current organization unless --no-verifyuse (2)
text
use --clear Unbind this foldercurrent
text
current [--json] The project this folder is bound to (PHILLIP_PROJECT overrides the file)