141 + --all-remotes(-a) # Show all tracking and non-tracking remote bookmarks including the ones whose targets are synchronized with the local bookmarks
142 + --remote: string # Show all tracking and non-tracking remote bookmarks belonging to this remote
143 + --tracked(-t) # Show remote tracked bookmarks only. Omits local Git-tracking bookmarks by default
144 + --conflicted(-c) # Show conflicted bookmarks only
145 + ...names: string # Show bookmarks whose local name matches
146 + --revisions(-r): string # Show bookmarks whose local targets are in the given revisions
147 + --template(-T): string # Render each bookmark using the given template
148 + --repository(-R): string # Path to repository to operate on
149 + --ignore-working-copy # Don't snapshot the working copy, and don't update it
315 + --all-remotes(-a) # Show all tracking and non-tracking remote bookmarks including the ones whose targets are synchronized with the local bookmarks
316 + --remote: string # Show all tracking and non-tracking remote bookmarks belonging to this remote
317 + --tracked(-t) # Show remote tracked bookmarks only. Omits local Git-tracking bookmarks by default
318 + --conflicted(-c) # Show conflicted bookmarks only
319 + ...names: string # Show bookmarks whose local name matches
320 + --revisions(-r): string # Show bookmarks whose local targets are in the given revisions
321 + --template(-T): string # Render each bookmark using the given template
322 + --repository(-R): string # Path to repository to operate on
323 + --ignore-working-copy # Don't snapshot the working copy, and don't update it
1150 + --source(-s): string # Fix files in the specified revision(s) and their descendants. If no revisions are specified, this defaults to the `revsets.fix` setting, or `reachable(@, mutable())` if it is not set
1183 +source: string # URL or path of the Git repo to clone
1184 + destination?: string # Specifies the target directory for the Jujutsu repository clone. If not provided, defaults to a directory named after the last component of the source URL. The full directory path will be created if it doesn't exist
1185 + --remote: string # Name of the newly created remote
1186 + --colocate # Whether or not to colocate the Jujutsu repo with the git repo
1187 + --depth: string # Create a shallow clone of the given depth
1188 + --repository(-R): string # Path to repository to operate on
1189 + --ignore-working-copy # Don't snapshot the working copy, and don't update it
1251 + destination?: string # The destination directory where the `jj` repo will be created. If the directory does not exist, it will be created. If no directory is given, the current directory is used
1252 + --colocate # Specifies that the `jj` repo should also be a valid `git` repo, allowing the use of both `jj` and `git` commands in the same directory
1253 + --git-repo: string # Specifies a path to an **existing** git repository to be used as the backing git repo for the newly created `jj` repo
1254 + --repository(-R): string # Path to repository to operate on
1255 + --ignore-working-copy # Don't snapshot the working copy, and don't update it
1547 + offset?: string # How many revisions to move forward. Advances to the next child by default
1548 + --edit(-e) # Instead of creating a new working-copy commit on top of the target commit (like `jj new`), edit the target commit directly (like `jj edit`)
1764 + --branch(-b): string # Rebase the whole branch relative to destination's ancestors (can be repeated)
1765 + --source(-s): string # Rebase specified revision(s) together with their trees of descendants (can be repeated)
1766 + --revisions(-r): string # Rebase the given revisions, rebasing descendants onto this revision's parent(s)
1767 + --destination(-d): string # The revision(s) to rebase onto (can be repeated to create a merge commit)
1768 + --insert-after(-A): string # The revision(s) to insert after (can be repeated to create a merge commit)
1769 + --after: string # The revision(s) to insert after (can be repeated to create a merge commit)
1770 + --insert-before(-B): string # The revision(s) to insert before (can be repeated to create a merge commit)
1771 + --before: string # The revision(s) to insert before (can be repeated to create a merge commit)
1772 + --skip-empty # Deprecated. Use --skip-emptied instead
1773 + --skip-emptied # If true, when rebasing would produce an empty commit, the commit is abandoned. It will not be abandoned if it was already empty before the rebase. Will never skip merge commits with multiple non-empty parents
1774 + --repository(-R): string # Path to repository to operate on
1775 + --ignore-working-copy # Don't snapshot the working copy, and don't update it
1790 + --list(-l) # Instead of resolving one conflict, list all the conflicts
1791 + --tool: string # Specify 3-way merge tool to be used
1792 + ...paths: string # Restrict to these paths when searching for a conflict to resolve. We will attempt to resolve the first conflict we can find. You can use the `--list` argument to find paths to use here
1793 + --repository(-R): string # Path to repository to operate on
1794 + --ignore-working-copy # Don't snapshot the working copy, and don't update it
2302 + --revision(-r): string # A list of parent revisions for the working-copy commit of the newly created workspace. You may specify nothing, or any number of parents
2303 + --sparse-patterns: string@"nu-complete jj workspace add sparse_patterns"# How to handle sparse patterns when creating a new workspace
2304 + --repository(-R): string # Path to repository to operate on
2305 + --ignore-working-copy # Don't snapshot the working copy, and don't update it
10 + --color: string@"nu-complete pueue color"# Colorize the output; auto enables color output when connected to a tty
11 + --config(-c): string # If provided, Pueue only uses this config file. This path can also be set via the "PUEUE_CONFIG_PATH" environment variable. The commandline option overwrites the environment variable!
12 + --profile(-p): string # The name of the profile that should be loaded from your config file
17 +# Enqueue a task for execution. There're many different options when scheduling a task. Check the individual option help texts for more information. Furthermore, please remember that scheduled commands are executed via your system shell. This means that the command needs proper shell escaping. The safest way to preserve shell escaping is to surround your command with quotes, for example: pueue add 'ls $HOME && echo "Some string"'
20 + --working-directory(-w): string # Specify current working directory
21 + --escape(-e) # Escape any special shell characters (" ", "&", "!", etc.). Beware: This implicitly disables nearly all shell specific syntax ("&&", "&>")
23 + --stashed(-s) # Create the task in Stashed state. Useful to avoid immediate execution if the queue is empty
24 + --delay(-d): string # Prevents the task from being enqueued until 'delay' elapses. See "enqueue" for accepted formats
25 + --group(-g): string # Assign the task to a group. Groups kind of act as separate queues. I.e. all groups run in parallel and you can specify the amount of parallel tasks for each group. If no group is specified, the default group will be used
26 + --after(-a): string # Start the task once all specified tasks have successfully finished. As soon as one of the dependencies fails, this task will fail as well
27 + --priority(-o): string # Start this task with a higher priority. The higher the number, the faster it will be processed
28 + --label(-l): string # Add some information for yourself. This string will be shown in the "status" table. There's no additional logic connected to it
29 + --print-task-id(-p) # Only return the task id instead of a text. This is useful when working with dependencies
59 +# Resume operation of specific tasks or groups of tasks. By default, this resumes the default group and all its tasks. Can also be used force-start specific tasks.
68 +# Restart failed or successful task(s). By default, identical tasks will be created and enqueued, but it's possible to restart in-place. You can also edit a few properties, such as the path and the command, before restarting.
70 + ...task_ids: string # Restart these specific tasks
71 + --all-failed(-a) # Restart all failed tasks across all groups. Nice to use in combination with `-i/--in-place`
72 + --failed-in-group(-g): string # Like `--all-failed`, but only restart tasks failed tasks of a specific group. The group will be set to running and its paused tasks will be resumed
73 + --start-immediately(-k) # Immediately start the tasks, no matter how many open slots there are. This will ignore any dependencies tasks may have
74 + --stashed(-s) # Set the restarted task to a "Stashed" state. Useful to avoid immediate execution
75 + --in-place(-i) # Restart the task by reusing the already existing tasks. This will overwrite any previous logs of the restarted tasks
76 + --not-in-place # Restart the task by creating a new identical tasks. Only applies, if you have the restart_in_place configuration set to true
77 + --edit(-e) # Edit the tasks' commands before restarting
78 + --edit-path(-p) # Edit the tasks' paths before restarting
79 + --edit-label(-l) # Edit the tasks' labels before restarting
80 + --edit-priority(-o) # Edit the tasks' priorities before restarting
84 +# Either pause running tasks or specific groups of tasks. By default, pauses the default group and all its tasks. A paused queue (group) won't start any new tasks.
96 + ...task_ids: string # Kill these specific tasks
97 + --group(-g): string # Kill all running tasks in a group. This also pauses the group
98 + --all(-a) # Kill all running tasks across ALL groups. This also pauses all groups
99 + --children(-c) # Deprecated: this switch no longer has any effect
100 + --signal(-s): string # Send a UNIX signal instead of simply killing the process. DISCLAIMER: This bypasses Pueue's process handling logic! You might enter weird invalid states, use at your own descretion
111 +# Edit the command, path, label, or priority of a stashed or queued task. By default only the command is edited. Multiple properties can be added in one go.
158 + ...query: string # Users can specify a custom query to filter for specific values, order by a column or limit the amount of tasks listed. Use `--help` for the full syntax definition
159 + --json(-j) # Print the current state as json to stdout. This does not include the output of tasks. Use `log -j` if you want everything
160 + --group(-g): string # Only show tasks of a specific group
161 + --help(-h) # Print help (see more with '--help')
164 +# Accept a list or map of JSON pueue tasks via stdin and display it just like "pueue status". A simple example might look like this: pueue status --json | jq -c '.tasks' | pueue format-status
170 +# Display the log output of finished tasks. Only the last few lines will be shown by default. If you want to follow the output of a task, please use the "follow" subcommand.
172 + ...task_ids: string # View the task output of these specific tasks
173 + --json(-j) # Print the resulting tasks and output as json. By default only the last lines will be returned unless --full is provided. Take care, as the json cannot be streamed! If your logs are really huge, using --full can use all of your machine's RAM
174 + --lines(-l): string # Only print the last X lines of each task's output. This is done by default if you're looking at multiple tasks
181 + task_id?: string # The id of the task you want to watch. If no or multiple tasks are running, you have to specify the id. If only a single task is running, you can omit the id
182 + --lines(-l): string # Only print the last X lines of the output before following
186 +# Wait until tasks are finished. By default, this will wait for all tasks in the default group to finish. Note: This will also wait for all tasks that aren't somehow 'Done'. Includes: [Paused, Stashed, Locked, Queued, ...]
215 +# Set the amount of allowed parallel tasks By default, adjusts the amount of the default group. No tasks will be stopped, if this is lowered. This limit is only considered when tasks are scheduled.
237 +# Enqueue a task for execution. There're many different options when scheduling a task. Check the individual option help texts for more information. Furthermore, please remember that scheduled commands are executed via your system shell. This means that the command needs proper shell escaping. The safest way to preserve shell escaping is to surround your command with quotes, for example: pueue add 'ls $HOME && echo "Some string"'
257 +# Resume operation of specific tasks or groups of tasks. By default, this resumes the default group and all its tasks. Can also be used force-start specific tasks.
261 +# Restart failed or successful task(s). By default, identical tasks will be created and enqueued, but it's possible to restart in-place. You can also edit a few properties, such as the path and the command, before restarting.
265 +# Either pause running tasks or specific groups of tasks. By default, pauses the default group and all its tasks. A paused queue (group) won't start any new tasks.
277 +# Edit the command, path, label, or priority of a stashed or queued task. By default only the command is edited. Multiple properties can be added in one go.
297 +# Accept a list or map of JSON pueue tasks via stdin and display it just like "pueue status". A simple example might look like this: pueue status --json | jq -c '.tasks' | pueue format-status
301 +# Display the log output of finished tasks. Only the last few lines will be shown by default. If you want to follow the output of a task, please use the "follow" subcommand.
309 +# Wait until tasks are finished. By default, this will wait for all tasks in the default group to finish. Note: This will also wait for all tasks that aren't somehow 'Done'. Includes: [Paused, Stashed, Locked, Queued, ...]
325 +# Set the amount of allowed parallel tasks By default, adjusts the amount of the default group. No tasks will be stopped, if this is lowered. This limit is only considered when tasks are scheduled.