Name the label table and a person's sub-tasks in do-epic's help
CI / tests (pull_request) Successful in 3m35s
CI / tests (pull_request) Successful in 3m35s
This commit is contained in:
@@ -46,6 +46,7 @@ HELP = f"""usage: do-epic <EPIC-KEY> [--status]
|
||||
Runs the chunks of one Jira epic, such as ABC-12, each in its own window of the tmux session epic-<EPIC-KEY>.
|
||||
Before it starts chunks, do-epic <EPIC-KEY> plans each open issue that has none of these labels:
|
||||
`repo:<name>` for its repo, `do-epic-claude` for work of Claude's that changes no repo, `do-epic-human` for a task of yours.
|
||||
A label that `[label-repos]` in config.toml maps to a repo counts as that repo's, and an issue with a sub-task a person filed is left as it is.
|
||||
Where such an issue changes several repos, it files a sub-task per repo. Otherwise it gives the issue its label, as repo-rule.md says.
|
||||
Where the rule leaves the label unclear, it asks you on the terminal. Answer with the label, or with Enter alone to leave the issue waiting.
|
||||
It then puts the scored issues that do-epic itself filed in order of score, by the `Score = ...` line under the epic's ## Scoring.
|
||||
|
||||
Reference in New Issue
Block a user