README.md + update dependencies

[?]

5GmofPYrEvoyQd4TVzxBDx6nVSC9mFJSPUziMDirav9D

Apr 23, 2024, 5:44 AM

FP36UDQAKAZMA2W6CJUUJWINLC6I67TUYKI7KL5LPN5MNBIKLXHAC

Dependencies

[2] VSIDBSWZ Add check and message when *All commands are run with no applicable resources
[3] TMXDVYNL Add command to amend changes
[4] SDZNGGDN Update README to add changelog and channel views as features
[5] XZNIYYVP Add information about supported to platforms to README requirements
[6] GPTHUH3N Add commands for unrecording changes
[7] KQF5G7P7 Fix typo in README and move conflict management to long term goals
[8] HSCLILFA Update installation instructions
[9] XX2BCMKG
[10] EBHCXOMV fix: getChangeFiles + update dependencies
[11] 3FBABWSM Add remotes view on the SCM panel
[12] YDCLFNEJ Add menu command for recording changes to specific files
[13] K3DIFEHD Remove basic channel management from MVP feature list
[14] YUVLBWV3 Populate resource groups for unrecorded and untracked changes
[15] FMKT2AXU Remove outdated issues from README.md
[16] B4SKYP3Y Add repository model and add steps to initialize it
[17] 4IGTXYXQ Found a couple of typos in the README.md file. “folloow” -> “follow” “vcse” -> “vsce”
[18] L44OILGK Add reset command to resource state context menu
[19] TPJNM4C4 Show only the changes which are not in the current channel on the channel view
[20] 64J6B76F Add command to rename channels
[21] NL47PGQC Update README
[22] NCBEWRYE Initialize Repository
[23] MGRAFWDZ Add commands for applying changes to channels
[24] RKZTS7RM Fix globs in ignore file
[25] AJL57OX6 Remove diff from roadmap
[26] WW67NYZV Configure eslint for JS standard formatting
[27] 2OX32U3O Add conflict management to MVP features
[28] MU6ZNUYZ Integrate recordAll command with input box
[29] 6LCROYAR Add known issue with deleted file names to README
[30] 6ONRFFRG First pass of file decorations
[31] BOS2K4SQ Add signing changes feature to README
[32] SVUCEKQO Add previously untracked .ignore files and .yarnrc
[33] H3GAPFUC Add pijul.recordAll command
[34] MO3G3S2V Cleanup commands available in the command palette
[35] BIEL6Z5J Update resource groups to use custom interface
[*] ZGMIJNFV Create pijul.ts for executing commands using the Pijul CLI
[*] 22ZBCRAN

Change contents

replacement in yarn.lock at line 1099

[10.40741]→[10.40741:40957](∅→∅)

version: 1.0.30001611
resolution: "caniuse-lite@npm:1.0.30001611"
checksum: 10c0/e6d6549a42b811212f6c4ef2798c45ab5a19484aaee0fa550ec20632a49638d3e53b64e088664d2efab0c5a278d1f8d1dec4654fbce11194e6ec1dc4ba5df466

[10.40741]

[10.40957]

version: 1.0.30001612
resolution: "caniuse-lite@npm:1.0.30001612"
checksum: 10c0/d6b405ff06f4e913bc779f9183fa68001c9d6b8526a7dd1b99c60587dd21a01aa8def3d8462cf6214f0181f1c21b9245611ff65241cf9c967fc742e86ece5065
replacement in yarn.lock at line 1540

[10.56286]→[10.56286:56500](∅→∅)

version: 1.4.745
resolution: "electron-to-chromium@npm:1.4.745"
checksum: 10c0/2dd1842e0ee84f88e78ee6e81dbd9dd554a589cf612ab2e5920d8be837aaea78b4c00cf189e545ee25d36777514fed80c11c9a867b2194f94f173d063873ec18

[10.56286]

[10.56500]

version: 1.4.746
resolution: "electron-to-chromium@npm:1.4.746"
checksum: 10c0/1ff47105510e9a6dbc542d7165b88e030c8f2c815b30683ca05d8bc1a24e8f03e57caa0dc03959b08860b0465f9645edea5c682400da5b79b71ce9ddbb89a3d6
replacement in yarn.lock at line 3594

[10.128791]→[10.128791:128845](∅→∅)

version: 3.60.0
resolution: "node-abi@npm:3.60.0"

[10.128791]

[11.10544]

version: 3.61.0
resolution: "node-abi@npm:3.61.0"
replacement in yarn.lock at line 3598

[10.128871]→[10.128871:129017](∅→∅)

checksum: 10c0/e375d13b2c9ed60d233cf3943d34a29b7502350626508659b8097cb9ce12e97263f8931c5fd177a974681e3ca6518d6f8a6ae2bc6b3aab0e0bd40970fb6599c8

[10.128871]

[10.129017]

checksum: 10c0/ba1e248e69138a8b1cde9332910e4475f6238d2d72aad0f16232c262cd19438c3878d11eed03c27c2494496cc645c1c1e9f1ce49a2653ae4fbd2dc98c76f4ef2
replacement in yarn.lock at line 4785

[10.170436]→[10.170436:170488](∅→∅)

version: 5.30.3
resolution: "terser@npm:5.30.3"

[10.170436]

[11.91946]

version: 5.30.4
resolution: "terser@npm:5.30.4"
replacement in yarn.lock at line 4794

[10.170653]→[10.170653:170799](∅→∅)

checksum: 10c0/ab5a8afef2e7a3b12a0fd17f9ff984fe02aefa945985eb139ab9984280d523a1104021eda889a7f993b69a67574ceb8fd0db8b76e5efc6a7607246db51bcc0b6

[10.170653]

[10.170799]

checksum: 10c0/c18b7d7cf01e079e96fd95e267ea1c2e22a098965c847d32c507a2f79f8d06f8107333184a3a9371693e072ab9dbc53a0a03e7d089044f9e3eae64589b360e4f
replacement in src/repository.ts at line 3

[11.57]→[6.0:101](∅→∅)

import { IUnrecordOptions, PijulChange, PijulChannel, Repository as BaseRepository } from './pijul';

[11.57]

[11.135]

import { Repository as BaseRepository, IUnrecordOptions, PijulChange, PijulChannel } from './pijul';
replacement in src/repository.ts at line 174

[11.799]→[11.799:904](∅→∅)

async recordChanges (resourceStates: SourceControlResourceState[], message? : string): Promise<void> {

[11.799]

[11.904]

async recordChanges (resourceStates: SourceControlResourceState[], message?: string): Promise<void> {
replacement in src/repository.ts at line 221

[11.155]→[11.553:615](∅→∅)

async recordAllChanges (message? : string): Promise<void> {

[11.155]

[2.0]

async recordAllChanges (message?: string): Promise<void> {
replacement in src/repository.ts at line 242

[3.326]→[3.326:387](∅→∅)

async amendAllChanges (message? : string): Promise<void> {

[3.326]

[3.387]

async amendAllChanges (message?: string): Promise<void> {
replacement in src/pijul.ts at line 510

[10.192705]→[10.192705:192726](∅→∅)

return [...diff]

[10.192705]

[11.1794]

return [...diff];
file addition: pijul-vscode-0.0.1.vsix (----------)

[9.1]
edit in README.md at line 2

[11.20]→[11.111039:111040](∅→∅),[11.111039]→[11.111039:111040](∅→∅),[11.111040]→[11.21:151](∅→∅),[11.151]→[11.111179:111180](∅→∅),[11.111179]→[11.111179:111180](∅→∅),[11.111180]→[11.152:379](∅→∅),[11.379]→[11.111192:111193](∅→∅),[11.111192]→[11.111192:111193](∅→∅),[11.111193]→[11.380:392](∅→∅)

Pijul for VS Code is an extension for Visual Studio Code which adds integration with Pijul as a source control management system.

Why develop my own extension instead of contributing to the existing one? It didn't even occur to me to check if one already existed
when I started, and when I did my own extension had enough distinct features to set it apart.

## Features
replacement in README.md at line 3

[11.111336]→[8.123:263](∅→∅),[8.263]→[11.533:596](∅→∅),[11.533]→[11.533:596](∅→∅)

At present, this extension offers _most_ of the basic features necessary for local Pijul development on a single channel. It includes basic
commands for initializing a repository in a VS Code workspace.

[11.111336]

[11.111419]

[Pijul](https://pijul.org/) is a distributed version control system that is easy to learn and use.
This **experimental beta-version** extension provides access from VS Code to the essential features of Pijul:
replacement in README.md at line 8

[11.751]→[11.0:86](∅→∅),[11.86]→[4.0:50](∅→∅),[4.50]→[11.111460:111461](∅→∅),[11.86]→[11.111460:111461](∅→∅),[11.751]→[11.111460:111461](∅→∅),[11.111460]→[11.111460:111461](∅→∅),[11.111461]→[11.752:812](∅→∅),[11.812]→[11.111629:111630](∅→∅),[11.111629]→[11.111629:111630](∅→∅),[11.111786]→[11.111786:111787](∅→∅),[11.111787]→[11.813:951](∅→∅),[11.951]→[5.0:294](∅→∅)

- VS Code comparison integration for diffing files with their last recorded versions.
- Basic views for the change log and the channels

Everything else still needs to be done on the command line.

Requires an existing Pijul installation. [Instructions for installing Pijul can be found here](https://pijul.org/manual/installing.html).
The primary development environment for the extension is WSL2 and at this early stage I can't guarantee that it will work on other platforms.
If you are using or have tried using the extension on a different platform, please feel free to open a discussion with any issues you have encountered.

[11.751]

[11.111896]

- VS Code comparison integration for diffing working files with their last recorded versions.
- Basic views for the change log and the channels.
replacement in README.md at line 11

[11.112071]→[11.112071:112087](∅→∅)

## Known Issues

[11.111897]

[11.112087]

Other operations need to be done using Pijul's [command line interface](https://pijul.org/manual/reference.html) in a terminal.
replacement in README.md at line 16

[11.112202]→[11.1062:1191](∅→∅)

Pijul for VS Code hasn't been published on the extension marketplace yet, so it needs to be built and installed from the source.

[11.112202]

[11.0]

Pijul for VS Code hasn't been published on the extension marketplace yet, so it needs to be installed manually.
replacement in README.md at line 19

[11.112337]→[11.1223:1295](∅→∅)

1. Clone the repository
2. Install Visual Studio Code Extensions (VSCE)

[11.112337]

[8.264]

1. [Install pijul](https://pijul.org/manual/installing.html) (Tested with 1.0.0-beta.9)
2. Make sure that pijul is in the PATH: `pijul --version`
3. Create an identity: `pijul identity new`
3. Clone this repository: `pijul clone https://nest.pijul.com/GarettWithOneR/pijul-vscode`
4. In VS Code, open the Command Palette (Ctrl + Shift + P) and run the "Extensions: Install from VSIX..." command to install the `pijul-vscode-0.0.1.vsix` file in the local directory created by the previous step.
replacement in README.md at line 25

[8.265]→[11.1295:1299](∅→∅),[11.1295]→[11.1295:1299](∅→∅),[11.1299]→[8.266:300](∅→∅),[8.300]→[11.1319:1323](∅→∅),[11.1319]→[11.1319:1323](∅→∅)

```
npm install --global @vscode/vsce
```

[8.265]

[8.301]

To activate Pijul version control in a folder, use `pijul init`.
replacement in README.md at line 27

[8.302]→[11.1323:1348](∅→∅),[11.1323]→[11.1323:1348](∅→∅)

3. Package the extension

[8.302]

[8.303]

Feedback on this extension [is welcome](https://nest.pijul.com/GarettWithOneR/pijul-vscode/discussions).
edit in README.md at line 29

[8.304]→[8.304:406](∅→∅),[8.406]→[11.31:44](∅→∅),[11.1352]→[11.31:44](∅→∅),[11.44]→[11.1365:1369](∅→∅),[11.1365]→[11.1365:1369](∅→∅)

```bash
# Windows users might need to set env var NODE_OPTIONS=--openssl-legacy-provider vsce package
vsce package
```
replacement in README.md at line 30

[8.408]→[8.408:568](∅→∅)

4. In VS Code, open the Command Palette (Ctrl + Shift + P) and run the "Extensions: Install from VSIX..." to install the VSIX file you created in the last step

[8.408]

[11.112365]

## Contributing
replacement in README.md at line 32

[11.112366]→[11.1531:1542](∅→∅)

## Roadmap

[11.112366]

[11.112474]

Pijul for VS Code welcomes all contributions.
Areas of development include:
replacement in README.md at line 35

[11.112475]→[11.1543:1758](∅→∅)

With the eventual goal of releasing on the Extension Marketplace with the same level of quality as other source control extensions,
there are a number of areas which will require a great deal of further refinement:

[11.112475]

[8.569]

- make all Pijul commands available from VS Code
- properly handle move and deletion of files
- show diff for past changes
replacement in README.md at line 39

[8.570]→[11.1758:1927](∅→∅),[11.1758]→[11.1758:1927](∅→∅)

- Proper handling of VS Code workspaces with multiple folders
- Automatic detection of Pijul installations
- More robust .ignore file handling
- Greater configurability

[8.570]

[11.112500]

To set-up your environment for [the development of a VS Code Extension](https://code.visualstudio.com/api/get-started/your-first-extension):
replacement in README.md at line 41

[11.112501]→[11.228:390](∅→∅)

There are also a number of Pijul features which still need to be implemented to reach a publishable minimum viable product, suitable for local Pijul development:

[11.112501]

[8.571]

1. [Install Node](https://nodejs.org/en/learn/getting-started/how-to-install-nodejs), e.g., using [nvm](https://github.com/nvm-sh/nvm?tab=readme-ov-file#install--update-script):
replacement in README.md at line 43

[11.390]→[11.2087:2134](∅→∅),[8.572]→[11.2087:2134](∅→∅),[11.2087]→[11.2087:2134](∅→∅),[11.2134]→[7.0:25](∅→∅),[7.25]→[11.391:409](∅→∅),[11.2206]→[11.391:409](∅→∅)

- Amending changes
- Moving and removing files
- Ignore file management
- Signing changes

[8.572]

[11.112613]

```bash
nvm install node
```
replacement in README.md at line 47

[11.112614]→[11.2207:2368](∅→∅)

In the long term, I would like to offer more in-depth Pijul integration, with the goal of providing a better experience than can be offered on the command line:

[11.112614]

[8.573]

2. Install dependencies
replacement in README.md at line 49

[8.574]→[11.2368:2424](∅→∅),[11.2368]→[11.2368:2424](∅→∅),[11.2457]→[11.2457:2530](∅→∅),[11.2530]→[7.26:48](∅→∅)

- Remote management
- Inline `pijul credit` annotations
- IntelliJ style changeset system
- Splitting/Combining existing changes
- Conflict management

[8.574]

[11.112862]

```bash
npm install -gD yo generator-code yarn webpack webpack-cli ts-loader
npm install --global @vscode/vsce
yarn
```
replacement in README.md at line 55

[11.112863]→[11.2531:2621](∅→∅)

Each category probably could probably fit a couple more points that I haven't thought of.

[11.112863]

[11.112888]

3. Create the `.vsix` file
replacement in README.md at line 57

[11.112889]→[11.2622:2638](∅→∅)

## Contributing

[11.112889]

[11.113066]

```bash
vsce package --no-yarn
```
replacement in README.md at line 61

[11.113067]→[11.2639:2774](∅→∅)

Pijul for VS Code welcomes all contributions. Before contributing, please be sure to add the following hook to your Pijul config file:

[11.113067]

[8.575]

4. Add the following hook to your [Pijul config file](https://pijul.org/manual/configuration.html):
edit in README.md at line 67

[11.112088]→[11.0:126](∅→∅),[11.111630]→[11.111630:111646](∅→∅)

- On the Source Control View, deleted files show up as their parent directory (This is the result of a Pijul CLI limitation).
## Requirements
resolve order conflict in README.md at line 67

[8.581]
edit in README.md at line 67

[0.12228936]
edit in .ignore at line 8

[11.61]→[10.192958:192965](∅→∅)

*.vsix
file addition: pijul-vscode-0.0.1.vsix (----------)

[38.1]