gt-milestone-issue-add1
Add issues or pull requests to a milestone
Usage
gt milestone
issue
add
<milestone>
{<number> | <url>} ...
[flags]
Overview
Add issues or pull requests to a milestone
Arguments
A milestone can be supplied by its title, such as "v1.0", or by its ID. A number is an ID first, then a title; --by-name matches it as a title only. An issue can be supplied as argument in any of the following formats: - by number, e.g. "123" or "#123" - by URL, e.g. "https://gitea.com/OWNER/REPO/issues/123" - by repository and number, e.g. "OWNER/REPO#123" Several issues must be in one repository. Next to "OWNER/REPO#123" or a URL, "124" means OWNER/REPO#124, unless gt targets another repository otherwise, such as the clone's, --repo or GITEA_CLI_REPO: then the command fails, and the number must be qualified.
Json fields
assignees, author, body, comments, created_at, due_date, id, kind, labels, milestone, number, ref, state, title, updated_at, url
Options
--by-name[=false]
Match a numeric milestone argument as a title rather than an ID
-h, --help[=false]
help for add
Options inherited from parent commands
--csv[=""]
Output CSV with the specified comma-separated fields, or all fields
--cwd=""
Working directory for repository discovery
--debug[=false]
Log the method, URL, status, and duration of each HTTP request to stderr
--host=""
Gitea instance URL, including any base path
--interactive[=false]
Allow prompts with machine output
-q, --jq=""
Filter JSON output using a jq expression; implies --json
--json[=""]
Output JSON with the specified comma-separated fields, or all fields
--no-input[=false]
Disable prompts and implicit editor/browser interactions
--remote=""
Git remote used for repository discovery
-R, --repo=""
Select a repository as OWNER/REPO or URL
--sudo=""
Perform API requests as this user (requires an administrator account)
--user=""
Account name on the selected instance
Examples
$ gt milestone issue add v1.0 12 $ gt milestone issue add v1.0 12 13 '#14'