You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/development.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -40,9 +40,9 @@ npm run build -ws
40
40
## Make changes
41
41
42
42
1. Open the workspace in VS Code `File -> Open Workspace from File...`: `/workspaces/vscode-github-actions.code-workspace`
43
-
- If you're doing local development, replace `workspaces` with the folder you created above (`vscode` in the example)
43
+
- If you're doing local development, replace `/workspaces` with the folder you created above (`~/vscode` in the example)
44
44
1. Make change to any of the packages
45
-
1. Build them all with `npm run build -ws` in `/workspaces/` (or `/vscode/` for local dev)
45
+
1. Build them all with `npm run build -ws` in `/workspaces/` (or `~/vscode/` for local dev)
46
46
1. Uninstall or disable the Actions extension in your development instance of VS Code
47
47
1. Start and debug extension with the `Watch & Launch Extension` configuration from the "Run and Debug" side panel menu
48
48
1. Open a workspace in the remote extension host that contains workflow files in the `.github/workflows` directory
@@ -51,9 +51,9 @@ npm run build -ws
51
51
52
52
Once you're happy with your changes, publish the changes to the respective packages. You might have to adjust package versions, so if you made a change to `actions-workflow-parser` and increase the version there, you will have to consume the updated package in `actions-languageservice`.
53
53
54
-
`npm workspaces` hoists all dependencies into a shared `node_modules` folder at the root directory (`/workspaces/node_modules` or `/vscode/node_modules` for local dev) and also creates a single `package-lock.json` file there for the whole workspace. We don't want that when pushing changes back to the individual repos.
54
+
`npm workspaces` hoists all dependencies into a shared `node_modules` folder at the root directory (`/workspaces/node_modules` or `~/vscode/node_modules` for local dev) and also creates a single `package-lock.json` file there for the whole workspace. We don't want that when pushing changes back to the individual repos.
55
55
56
-
There is a script in `/workspaces` (or `/vscode` for local dev): `update-package-locks.sh` that does an `npm install` in every package directory _without_ using workspaces. That way, the local `package-lock.json` file is generated correctly and can be pushed to the repository.
56
+
There is a script in `/workspaces` (or `~/vscode` for local dev): `update-package-locks.sh` that does an `npm install` in every package directory _without_ using workspaces. That way, the local `package-lock.json` file is generated correctly and can be pushed to the repository.
0 commit comments