pi-spaces 0.16.1 → 0.16.2

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/CHANGELOG.md CHANGED
@@ -6,6 +6,12 @@ commands and options and a patch version fixes.
6
6
 
7
7
  ## Unreleased
8
8
 
9
+ ## 0.16.2
10
+
11
+ ### Changed
12
+
13
+ - The skill tells how to pin a space to a repository with `pi-space pin` (pi-spaces-cli 0.18.0).
14
+
9
15
  ## 0.16.1
10
16
 
11
17
  ### Changed
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "pi-spaces",
3
- "version": "0.16.1",
3
+ "version": "0.16.2",
4
4
  "description": "Named spaces for Pi: keep several agent homes (sign-ins, packages, settings) and pick one by name.",
5
5
  "license": "MIT",
6
6
  "author": "jals1212",
@@ -33,6 +33,7 @@ Use when a task depends on which Pi agent home this session uses (settings, sign
33
33
  | Spaces folder | `PI_SPACES_DIR`, else the `dir` of the profile whose `home` is the base home, else `spaces` next to the base home (`PI_SPACES_BASE_HOME`, else this home) |
34
34
  | Profiles, or why a variable differs per space | The config file (`PI_SPACES_CONFIG`, else `config.toml` or `config.json` in `~/.config/pi-spaces`, then in `~/.pi-spaces`): a profile's `spaceEnv` variables are set only inside spaces (`{home}` the agent home, `{space}` the space's root folder and `{name}` filled in) and removed in base; without `spaceEnv` whatever a program keeps outside its agent home is shared with base |
35
35
  | Pick a space from a shell | bare `pi-space` on a terminal opens a picker of every profile's spaces (`<profile>/<name>`, `base` included) and starts Pi in the one chosen |
36
+ | Pin a space to a repository (like `.nvmrc`) | `pi-space pin <profile>/<name>` writes `.pi/pi-space/space` (one line `<profile>/<name>`) and a self-ignoring `.pi/pi-space/.gitignore` in the git root; a bare `pi-space` there or below then starts that space at once (a space named on the command line wins; `pi-space pick` opens the picker); `pi-space pin` shows it, `pi-space unpin` removes it. Only `pi-space` reads it, not Pi or `/space` |
36
37
  | Rename a space | User request only: `pi-space rename <profile>/<old> <new>`; the new name alone or with the same profile (`<profile>/<new>`), a space never changes profile; refused for base and for the space you are in |
37
38
  | Create a space | `pi-space new <profile>/<name>`, or ask the user for `/space new <name>` (this Pi's profile); `pi-space new` also runs the profile's setup command when there is one (or `--setup <cmd>` for one call), and asks whether the space declares the extension: pass `--extension` or `--no-extension` when running it for the user, since there is no terminal to answer |
38
39
  | Prepare a space for the program that runs Pi | `pi-space setup <profile>/<name>` (or `<profile>/base`, `<profile>/--every` for base then its spaces, or `--every` for the base and spaces of every profile with a setup, which pi has not by default; the profile's `commands.setup`): runs the setup command (`{home}` becomes the space's agent home, `{space}` its root folder and `{name}` its name) with the agent home as `PI_CODING_AGENT_DIR`; in base `{home}` is the profile's home and `{name}` is `base` |