slipway 0.1.0

data/man/man1/slipway-rollout-history.1

@@ -0,0 +1,28 @@
+.\" Generated by slipway 0.1.0. Do not edit.
+.TH "SLIPWAY-ROLLOUT-HISTORY" "1" "2026-09-30" "slipway 0.1.0" "Slipway Manual"
+.SH NAME
+slipway\-rollout\-history \- View rollout history
+.SH SYNOPSIS
+.SY "slipway rollout history"
+.I "(NAME | project/NAME)"\&
+.RI [ flags ]
+.YS
+.SH DESCRIPTION
+View the rollout history of a project.
+.PP
+Lists the revisions of the checked\-out branch, oldest first: each commit slipway moved the branch to, read from the entries of the branch's reflog whose subject starts with "slipway ", and the commit the branch stood at before such a move. REVISION numbers them from the oldest entry git still keeps, COMMIT is the commit, DATE the time the branch moved there, CHANGE\-CAUSE the move slipway made, and PINNED marks the revision spec.revision holds the project at. Nothing is fetched or written.
+.PP
+The history lasts as long as git keeps the reflog (gc.reflogExpire, 90 days by default; slipway never runs gc), and git keeps none under core.logAllRefUpdates=false. A project without history prints a notice on stderr and exits with status 0.
+.SH EXAMPLES
+.EX
+# View the rollout history of project hldr
+slipway rollout history hldr
+.EE
+.PP
+.EX
+# View the rollout history of project api in the work group
+slipway rollout history project/api \-n work
+.EE
+.SH "SEE ALSO"
+.BR slipway (1),
+.BR slipway\-rollout (1)

data/man/man1/slipway-rollout-pause.1

@@ -0,0 +1,21 @@
+.\" Generated by slipway 0.1.0. Do not edit.
+.TH "SLIPWAY-ROLLOUT-PAUSE" "1" "2026-09-30" "slipway 0.1.0" "Slipway Manual"
+.SH NAME
+slipway\-rollout\-pause \- Mark the provided project as paused
+.SH SYNOPSIS
+.SY "slipway rollout pause"
+.I "(NAME... | project/NAME...)"\&
+.RI [ flags ]
+.YS
+.SH DESCRIPTION
+Mark the provided projects as paused.
+.PP
+Sets spec.paused in the manifest of each named project. Paused projects are left alone by slipway fetch and slipway sync, which run no git command in them; slipway rollout undo still acts on them. Use slipway rollout resume to resume a paused project.
+.SH EXAMPLES
+.EX
+# Keep fetch and sync away from project dots
+slipway rollout pause dots
+.EE
+.SH "SEE ALSO"
+.BR slipway (1),
+.BR slipway\-rollout (1)

data/man/man1/slipway-rollout-resume.1

@@ -0,0 +1,21 @@
+.\" Generated by slipway 0.1.0. Do not edit.
+.TH "SLIPWAY-ROLLOUT-RESUME" "1" "2026-09-30" "slipway 0.1.0" "Slipway Manual"
+.SH NAME
+slipway\-rollout\-resume \- Resume a paused project
+.SH SYNOPSIS
+.SY "slipway rollout resume"
+.I "(NAME... | project/NAME...)"\&
+.RI [ flags ]
+.YS
+.SH DESCRIPTION
+Resume paused projects.
+.PP
+Removes spec.paused from the manifest of each named project, so slipway fetch and slipway sync act on it again. A project that is not paused prints not paused.
+.SH EXAMPLES
+.EX
+# Resume the paused project dots
+slipway rollout resume dots
+.EE
+.SH "SEE ALSO"
+.BR slipway (1),
+.BR slipway\-rollout (1)

data/man/man1/slipway-rollout-undo.1

@@ -0,0 +1,73 @@
+.\" Generated by slipway 0.1.0. Do not edit.
+.TH "SLIPWAY-ROLLOUT-UNDO" "1" "2026-09-30" "slipway 0.1.0" "Slipway Manual"
+.SH NAME
+slipway\-rollout\-undo \- Undo a previous rollout
+.SH SYNOPSIS
+.SY "slipway rollout undo"
+.I "(NAME | project/NAME)"\&
+.RI [ flags ]
+.YS
+.SH DESCRIPTION
+Roll back a project to a previous revision.
+.PP
+Moves the checked\-out branch to the revision before the current one, or to the one \-\-to\-revision names from slipway rollout history, and then writes that commit to spec.revision, so sync holds the project there until slipway rollout unpin. The branch moves back with git reset \-\-keep, only when its upstream holds every commit the move drops, and forward, to undo an undo, with git merge \-\-ff\-only. Untracked files and unstaged changes to files the move leaves alone are kept; git refuses a move that would overwrite a local change or an untracked file, and slipway refuses one that would overwrite an ignored file. A move back skips a project with staged changes, and a move forward one with staged or unstaged changes.
+.PP
+A project whose HEAD is detached, whose branch has no commits or no upstream that exists, that is in the middle of a merge, rebase or other operation, or whose branch has commits its upstream lacks, is skipped with the reason and nothing is moved or written. A paused project can be rolled back: pausing only keeps fetch and sync away.
+.PP
+The project prints one line, one of the results listed below, with a reason in parentheses and the details under it.
+.PP
+With \-\-dry\-run nothing is moved or written, and the line ends in (dry run).
+.SH OPTIONS
+.TP
+\fB\-\-to\-revision\fR \fIN\fR
+The revision to roll back to, as slipway rollout history numbers it. 0, the default, is the revision before the current one.
+.TP
+\fB\-\-dry\-run\fR
+Print what would change and write nothing.
+.SH RESULTS
+.TP
+\fBrolled back\fR
+The branch moved, or it already stood at the revision and only spec.revision changed. The detail names the commits it crossed and the command that lets sync follow the upstream again.
+.TP
+\fBunchanged\fR
+The branch already stood at the revision and spec.revision already held it.
+.TP
+\fBskipped (Reason)\fR
+Nothing moved and nothing was written. git could not read the repository (Missing, NotARepo, Unsafe, Unknown); the branch cannot move (Conflicted, Detached, Unborn, NoUpstream, Gone, InProgress); the history has no such revision (NoHistory, NoPrevious, UnknownRevision) or the repository no such commit (RevisionNotFound); a move back would drop commits the upstream lacks (LocalCommits) or staged changes (Dirty), or the revision is off the branch's history (Diverged); a move forward needs a tree without staged or unstaged changes (Dirty) and a revision on the upstream (OffUpstream); or git refused the move (WouldLoseChanges, WouldOverwrite for untracked or ignored files in the way, Busy, NotFastForward for a branch that moved since the check).
+.TP
+\fBdenied (Reason)\fR
+A partial clone had to fetch the files the move writes and the remote asked for a password, a passphrase or a host key (AuthRequired), as in slipway fetch.
+.TP
+\fBfailed (Reason)\fR
+The move ran past networkTimeout (Timeout) or git failed for another reason (Unknown), and spec.revision was not written, though a move stopped at the deadline keeps the files git had already written, as in slipway sync; or the branch moved but spec.revision could not be written (NotPinned), and the detail names the \-\-to\-revision command that writes it without moving the branch again.
+.SH "EXIT STATUS"
+.TP
+\fB0\fR
+The project was rolled back, or already stood at the revision and was held there.
+.TP
+\fB1\fR
+Runtime error, such as a missing resource or an unreadable manifest, or a project that was skipped or whose move was denied or failed.
+.TP
+\fB2\fR
+Usage error: unknown command, unknown flag or invalid argument.
+.TP
+\fB130\fR
+Interrupted by SIGINT.
+.SH EXAMPLES
+.EX
+# Roll back project hldr to the previous revision
+slipway rollout undo hldr
+.EE
+.PP
+.EX
+# Roll back project hldr to revision 3
+slipway rollout undo hldr \-\-to\-revision=3
+.EE
+.PP
+.EX
+# Show where undo would move project hldr, without moving or writing anything
+slipway rollout undo hldr \-\-dry\-run
+.EE
+.SH "SEE ALSO"
+.BR slipway (1),
+.BR slipway\-rollout (1)

data/man/man1/slipway-rollout-unpin.1

@@ -0,0 +1,21 @@
+.\" Generated by slipway 0.1.0. Do not edit.
+.TH "SLIPWAY-ROLLOUT-UNPIN" "1" "2026-09-30" "slipway 0.1.0" "Slipway Manual"
+.SH NAME
+slipway\-rollout\-unpin \- Stop holding a project at a revision
+.SH SYNOPSIS
+.SY "slipway rollout unpin"
+.I "(NAME... | project/NAME...)"\&
+.RI [ flags ]
+.YS
+.SH DESCRIPTION
+Stop holding projects at a revision.
+.PP
+Removes spec.revision from the manifest of each named project, so the next slipway sync fast\-forwards its branch onto its upstream again. The repository is left as it is. A project without spec.revision prints not pinned.
+.SH EXAMPLES
+.EX
+# Let project hldr follow its upstream again
+slipway rollout unpin hldr
+.EE
+.SH "SEE ALSO"
+.BR slipway (1),
+.BR slipway\-rollout (1)

data/man/man1/slipway-rollout.1

@@ -0,0 +1,36 @@
+.\" Generated by slipway 0.1.0. Do not edit.
+.TH "SLIPWAY-ROLLOUT" "1" "2026-09-30" "slipway 0.1.0" "Slipway Manual"
+.SH NAME
+slipway\-rollout \- Manage the rollout of a project
+.SH SYNOPSIS
+.SY "slipway rollout"
+.I COMMAND
+.RI [ flags ]
+.YS
+.SH DESCRIPTION
+Manage the rollout of a project.
+.PP
+Slipway records a revision each time it moves the checked\-out branch of a project: every fast\-forward of slipway sync and every slipway rollout undo leaves an entry in the branch's reflog, and the commit the branch stood at before such a move is a revision too. rollout history lists the revisions, rollout undo returns the branch to one of them and holds the project there with spec.revision, and rollout unpin lets sync follow the upstream again. rollout pause keeps fetch and sync away from a project until rollout resume.
+.SH COMMANDS
+.TP 9
+\fBhistory\fR
+View rollout history
+.TP 9
+\fBundo\fR
+Undo a previous rollout
+.TP 9
+\fBunpin\fR
+Stop holding a project at a revision
+.TP 9
+\fBpause\fR
+Mark the provided project as paused
+.TP 9
+\fBresume\fR
+Resume a paused project
+.SH "SEE ALSO"
+.BR slipway (1),
+.BR slipway\-rollout\-history (1),
+.BR slipway\-rollout\-undo (1),
+.BR slipway\-rollout\-unpin (1),
+.BR slipway\-rollout\-pause (1),
+.BR slipway\-rollout\-resume (1)

data/man/man1/slipway-sync.1

@@ -0,0 +1,90 @@
+.\" Generated by slipway 0.1.0. Do not edit.
+.TH "SLIPWAY-SYNC" "1" "2026-09-30" "slipway 0.1.0" "Slipway Manual"
+.SH NAME
+slipway\-sync \- Fetch projects and fast\-forward their branches
+.SH SYNOPSIS
+.SY "slipway sync"
+.I "[NAME... | project/NAME...]"\&
+.RI [ flags ]
+.YS
+.SH DESCRIPTION
+Fetch each selected project and fast\-forward its branch.
+.PP
+Runs in every project of the current group, in the projects named, in the ones a label selector matches, or with \-\-all\-groups in every project. Each project is fetched as slipway fetch fetches it and compared with its manifest as slipway diff compares it, and its checked\-out branch is fast\-forwarded onto its upstream when the branch tracks an upstream that still exists, is behind it without commits of its own, has no staged, unstaged or conflicted changes and no merge, rebase or other operation in progress. Untracked files do not stop it, and git refuses a fast\-forward that would overwrite one. Sync never merges, rebases, stashes, resets, switches a branch or changes a remote.
+.PP
+A project whose spec.syncPolicy is FetchOnly is only fetched, and one whose spec.paused is true is left alone: no git command runs in it. A project pinned by spec.revision is fast\-forwarded up to that commit instead of its upstream, only when its upstream holds the commit, never past it, and never moved back to it.
+.PP
+Each project prints one line, one of the results listed below, with a reason in parentheses and the details under it. The parallel setting caps how many projects fetch at once, fast\-forwards run one at a time, and the results print in the order the projects are listed.
+.PP
+With \-\-dry\-run nothing is fetched or written: the plan is made from the last fetch.
+.SH OPTIONS
+.TP
+\fB\-l\fR, \fB\-\-selector\fR \fIEXPR\fR
+Selector (label query) to filter on, supports '=', '==', '!=', 'in', 'notin' (e.g. \-l key1=value1,key2=value2,key3 in (value3)). Matching objects must satisfy all of the specified label constraints.
+.TP
+\fB\-A\fR, \fB\-\-all\-groups\fR
+If present, sync every project across all groups. The group in the current configuration is ignored even if specified with \-\-group.
+.TP
+\fB\-\-prune\fR
+Before fetching, remove any remote\-tracking references that no longer exist on the remote.
+.TP
+\fB\-\-dry\-run\fR
+Print what would change and write nothing.
+.SH RESULTS
+When more than one project ran, a count of the results closes the run on stderr. With \-\-dry\-run every line and the count end in (dry run). Ctrl\-C stops the git processes slipway started and exits with status 130; a fast\-forward it stops ends as one stopped at the deadline.
+.TP
+\fBfast\-forwarded\fR
+The branch moved. For a move onto the upstream, the detail names the commits it gained, as main a1b2c3d..e4f5a6b (3 commits), and the command that undoes the move; a move up to a spec.revision pin ends in (to the pinned revision).
+.TP
+\fBfetched\fR
+The fetch of a FetchOnly project moved refs; the refs follow as in slipway fetch.
+.TP
+\fBunchanged\fR
+The branch stayed where it was and nothing blocked it; the fetch may still have moved remote\-tracking refs.
+.TP
+\fBskipped (Reason)\fR
+The branch stayed where it was: a blocker stopped it, under the name slipway diff gives it; git refused the fast\-forward (WouldOverwrite for untracked files in the way, WouldLoseChanges for local changes git status does not show, Busy for a lock another git process holds on the index, HEAD or the branch, NotFastForward for a branch that gained a commit since the check); or the project was skipped before its fetch, as in slipway fetch (Missing, NotARepo, Unsafe, Unknown, NoRemote, LocalUpstream).
+.TP
+\fBpaused\fR
+spec.paused is true, so no git command ran in the project.
+.TP
+\fBdenied (Reason)\fR
+The fetch or the fast\-forward needed a password, a passphrase or a host key (AuthRequired), as in slipway fetch.
+.TP
+\fBfailed (Reason)\fR
+The fetch or the fast\-forward ran past networkTimeout (Timeout), used a transport protocols leaves out (ProtocolNotAllowed), or git failed for another reason (Unknown). A fast\-forward stopped at the deadline leaves the branch where it was, but the files git had already written stay in the working tree, and the detail names the command that lists them.
+.SH "EXIT STATUS"
+.TP
+\fB0\fR
+Every selected project was fast\-forwarded, fetched, left unchanged, skipped or paused.
+.TP
+\fB1\fR
+Runtime error, such as a missing resource or an unreadable manifest, or a project whose fetch or fast\-forward was denied or failed.
+.TP
+\fB2\fR
+Usage error: unknown command, unknown flag or invalid argument.
+.TP
+\fB130\fR
+Interrupted by SIGINT.
+.SH EXAMPLES
+.EX
+# Sync every project in the current group
+slipway sync
+.EE
+.PP
+.EX
+# Sync every project in every group
+slipway sync \-A
+.EE
+.PP
+.EX
+# Sync two projects of the work group
+slipway sync api web \-n work
+.EE
+.PP
+.EX
+# Show what sync would do from the last fetch, without contacting any remote
+slipway sync \-A \-\-dry\-run
+.EE
+.SH "SEE ALSO"
+.BR slipway (1)

data/man/man1/slipway-version.1

@@ -0,0 +1,17 @@
+.\" Generated by slipway 0.1.0. Do not edit.
+.TH "SLIPWAY-VERSION" "1" "2026-09-30" "slipway 0.1.0" "Slipway Manual"
+.SH NAME
+slipway\-version \- Print the version of slipway
+.SH SYNOPSIS
+.SY "slipway version"
+.RI [ flags ]
+.YS
+.SH DESCRIPTION
+Print the version of slipway, the Ruby it runs on and the platform.
+.SH EXAMPLES
+.EX
+# Print the version
+slipway version
+.EE
+.SH "SEE ALSO"
+.BR slipway (1)

data/man/man1/slipway.1

@@ -0,0 +1,243 @@
+.\" Generated by slipway 0.1.0. Do not edit.
+.TH "SLIPWAY" "1" "2026-09-30" "slipway 0.1.0" "Slipway Manual"
+.SH NAME
+slipway \- A kubectl\-style registry of the git repositories on your machine
+.SH SYNOPSIS
+.SY slipway
+.RI [ flags ]
+.I COMMAND
+.RI [ ARGS... ]\&
+.YS
+.SH DESCRIPTION
+A kubectl\-style registry of the git repositories on your machine.
+.PP
+A project is a registered git repository. get and describe show where each one
+stands, and fetch fetches them all without prompting. Its manifest can also
+declare where the repository should be: the remote, the branch and a commit to
+hold it at. diff shows where a repository differs from that, sync fast\-forwards
+the branches that can move without losing work, and rollout undo takes such a
+move back.
+.PP
+Projects live in groups the way pods live in namespaces. The group is
+"default", or the one SLIPWAY_GROUP or the group key sets, unless \-n
+is given, and \-A covers every group.
+.PP
+Resource types: projects (project, proj) and groups (group). Type words are case\-insensitive.
+.SH COMMANDS
+.SS "Basic Commands"
+.TP 15
+\fBget\fR
+Display one or many resources
+.TP 15
+\fBdescribe\fR
+Show details of one or many resources
+.TP 15
+\fBcreate\fR
+Create a resource by name
+.TP 15
+\fBapply\fR
+Apply a configuration to a resource by file name or stdin
+.TP 15
+\fBdelete\fR
+Delete resources by type and name
+.TP 15
+\fBedit\fR
+Edit a resource from the default editor
+.TP 15
+\fBlabel\fR
+Update the labels on a resource
+.TP 15
+\fBexplain\fR
+Get documentation for a resource
+.SS "Repository Commands"
+.TP 15
+\fBfetch\fR
+Fetch from the remote of each project
+.TP 15
+\fBdiff\fR
+Show where projects differ from their manifests
+.TP 15
+\fBsync\fR
+Fetch projects and fast\-forward their branches
+.TP 15
+\fBrollout\fR
+Manage the rollout of a project
+.SS "Settings Commands"
+.TP 15
+\fBconfig\fR
+Inspect the configuration in effect
+.TP 15
+\fBcompletion\fR
+Output shell completion code for the specified shell (bash, zsh, fish)
+.TP 15
+\fBman\fR
+Show the manual page of a command
+.SS "Other Commands"
+.TP 15
+\fBapi\-resources\fR
+Print the supported resource types
+.TP 15
+\fBhelp\fR
+Help about any command
+.TP 15
+\fBversion\fR
+Print the version of slipway
+.SH OPTIONS
+.TP
+\fB\-\-color\fR[=\fIWHEN\fR]
+When to use color in the output; a bare \-\-color means always. One of: auto, always, never.
+.TP
+\fB\-n\fR, \fB\-\-group\fR \fINAME\fR
+The group scope for this request.
+.TP
+\fB\-\-config\fR \fIPATH\fR
+Path to the configuration file.
+.TP
+\fB\-h\fR, \fB\-\-help\fR
+Print help and exit.
+.TP
+\fB\-V\fR, \fB\-\-version\fR
+Print the version and exit.
+.SH ENVIRONMENT
+.TP
+\fBSLIPWAY_CONFIG\fR
+Path of the configuration file; overridden by \-\-config.
+.TP
+\fBSLIPWAY_DATA_HOME\fR
+Directory holding the registry: group and project manifests.
+.TP
+\fBSLIPWAY_COLOR\fR
+Outranks the color key (see CONFIGURATION); \-\-color outranks both.
+.TP
+\fBSLIPWAY_THEME\fR
+Outranks the theme key (see CONFIGURATION).
+.TP
+\fBSLIPWAY_EDITOR\fR
+Outranks the editor key (see CONFIGURATION), VISUAL and EDITOR.
+.TP
+\fBSLIPWAY_GROUP\fR
+Outranks the group key (see CONFIGURATION); \-\-group outranks both.
+.TP
+\fBSLIPWAY_NETWORK_TIMEOUT\fR
+Outranks the networkTimeout key (see CONFIGURATION).
+.TP
+\fBSLIPWAY_PARALLEL\fR
+Outranks the parallel key (see CONFIGURATION).
+.TP
+\fBSLIPWAY_PROTOCOLS\fR
+Outranks the protocols key (see CONFIGURATION); the names are separated by colons, as in ssh:https.
+.TP
+\fBSLIPWAY_DEBUG\fR
+When non\-empty, unexpected errors also print their class and backtrace.
+.TP
+\fBNO_COLOR\fR
+When non\-empty, disables color in auto mode.
+.TP
+\fBFORCE_COLOR\fR
+When non\-empty, enables color in auto mode even without a terminal.
+.TP
+\fBCLICOLOR_FORCE\fR
+Same as FORCE_COLOR.
+.TP
+\fBVISUAL\fR
+Editor used by edit when SLIPWAY_EDITOR and the editor configuration key are unset.
+.TP
+\fBEDITOR\fR
+Editor used by edit when VISUAL is unset as well.
+.TP
+\fBXDG_CONFIG_HOME\fR
+Base of the configuration directory (default ~/.config).
+.TP
+\fBXDG_DATA_HOME\fR
+Base of the data directory (default ~/.local/share).
+.TP
+\fBTERM\fR
+When dumb, disables color in auto mode.
+.TP
+\fBMANPAGER\fR
+When non\-empty, slipway man leaves the pager palette alone.
+.TP
+\fBMANROFFOPT\fR
+Same as MANPAGER.
+.TP
+\fBLESS_TERMCAP_md\fR
+Same as MANPAGER.
+.TP
+\fBGROFF_NO_SGR\fR
+Same as MANPAGER.
+.TP
+\fBGIT_DIR, GIT_WORK_TREE, GIT_INDEX_FILE, GIT_NAMESPACE, GIT_OBJECT_DIRECTORY, GIT_ALTERNATE_OBJECT_DIRECTORIES\fR
+Ignored: every git command slipway runs starts without them, so an inherited value cannot point git at another repository.
+.SH FILES
+.TP
+\fI$XDG_CONFIG_HOME/slipway/config.yaml\fR
+Configuration file; see CONFIGURATION. Also set by \-\-config or SLIPWAY_CONFIG.
+.TP
+\fI$XDG_DATA_HOME/slipway/\fR
+Registry data: groups/NAME.yaml and projects/GROUP/NAME.yaml. Also set by SLIPWAY_DATA_HOME.
+.SH CONFIGURATION
+.TP
+\fBcolor\fR
+When to color output: auto, always or never. Default: auto.
+.TP
+\fBeditor\fR
+Command line of the editor that slipway edit opens.
+.TP
+\fBgroup\fR
+Group used when \-n is not given. Default: default.
+.TP
+\fBnetworkTimeout\fR
+Seconds, from 1 to 86400, a git network command may run before it is killed with the processes it started. Default: 60.
+.TP
+\fBparallel\fR
+How many git network commands run at once, from 1 to 16. Default: 4.
+.TP
+\fBprotocols\fR
+Transports git may use in network commands, as a list; any other transport is refused, and so are ext and fd. Add file for local mirrors. Default: ssh, https.
+.TP
+\fBtheme\fR
+Color theme: dark or light. Default: dark.
+.SH "EXIT STATUS"
+.TP
+\fB0\fR
+Success.
+.TP
+\fB1\fR
+Runtime error, such as a missing resource or an unreadable manifest.
+.TP
+\fB2\fR
+Usage error: unknown command, unknown flag or invalid argument.
+.TP
+\fB130\fR
+Interrupted by SIGINT.
+.PP
+The pages of these commands list their own statuses:
+.BR slipway\-diff (1),
+.BR slipway\-sync (1),
+.BR slipway\-rollout\-undo (1)
+.SH "SEE ALSO"
+.BR slipway\-get (1),
+.BR slipway\-describe (1),
+.BR slipway\-create (1),
+.BR slipway\-apply (1),
+.BR slipway\-delete (1),
+.BR slipway\-edit (1),
+.BR slipway\-label (1),
+.BR slipway\-explain (1),
+.BR slipway\-fetch (1),
+.BR slipway\-diff (1),
+.BR slipway\-sync (1),
+.BR slipway\-rollout (1),
+.BR slipway\-rollout\-history (1),
+.BR slipway\-rollout\-undo (1),
+.BR slipway\-rollout\-unpin (1),
+.BR slipway\-rollout\-pause (1),
+.BR slipway\-rollout\-resume (1),
+.BR slipway\-config (1),
+.BR slipway\-config\-view (1),
+.BR slipway\-config\-path (1),
+.BR slipway\-api\-resources (1),
+.BR slipway\-help (1),
+.BR slipway\-version (1),
+.BR slipway\-completion (1),
+.BR slipway\-man (1)