Luigit
repositories / pi-ext

pi-ext

bugabingas pi extensions

owned by admin

extensions/vcs-status/README.md

Raw
Rendered preview
vcs-status

vcs-status

Switching between projects and branches makes it easy to lose sight of where Pi is working and whether changes are pending. vcs-status keeps the current directory and Git or Jujutsu state visible during a Pi session.

Use

Nothing to invoke. Start Pi inside a Git or Jujutsu repository and inspect the workspace area for its path, repository identity, and change state. Git shows branch and working-tree signals such as modified, staged, untracked, conflicted, stash, and remote divergence. Jujutsu shows the current change, local bookmarks, and empty, conflict, or divergent signals. Outside a repository, it shows the current directory only. The status refreshes after Pi finishes work or a tool runs.

If repository-status commands need more time in your environment, increase the timeout:

{ "vcs-status": { "timeoutMs": 5000 } }

Put project settings only in a trusted project because Pi ignores project settings until trust is granted.

Installation

Reference

Setting names

Setting Environment
vcs-status.timeoutMs PI_VCS_STATUS_TIMEOUT_MS

Changelog.

<img src="assets/banner.svg" alt="vcs-status" height="70">

# vcs-status

Switching between projects and branches makes it easy to lose sight of where Pi is working and whether changes are pending.
vcs-status keeps the current directory and Git or Jujutsu state visible during a Pi session.

## Use

Nothing to invoke.
Start Pi inside a Git or Jujutsu repository and inspect the workspace area for its path, repository identity, and change state.
Git shows branch and working-tree signals such as modified, staged, untracked, conflicted, stash, and remote divergence.
Jujutsu shows the current change, local bookmarks, and empty, conflict, or divergent signals.
Outside a repository, it shows the current directory only.
The status refreshes after Pi finishes work or a tool runs.

If repository-status commands need more time in your environment, increase the timeout:

```json
{ "vcs-status": { "timeoutMs": 5000 } }
```

Put project settings only in a trusted project because Pi ignores project settings until trust is granted.

[Installation](../../README.md#install)

## Reference

<!-- config:start -->
### Setting names

| Setting | Environment |
| --- | --- |
| `vcs-status.timeoutMs` | `PI_VCS_STATUS_TIMEOUT_MS` |
<!-- config:end -->

[Changelog](./CHANGELOG.md).