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: README.md
+15Lines changed: 15 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -133,6 +133,21 @@ Note that this will not work from a Mac OS host per [this Docker issue](https://
133
133
134
134
You can enable debugging on either the server or the client by setting the environmental variable `GIT_CREDENTIAL_FORWARDER_DEBUG` to `true`.
135
135
136
+
## Development
137
+
138
+
### Publishing to npm
139
+
140
+
This project uses GitHub Actions to automatically publish to npm when a new release is created. To set this up:
141
+
142
+
1. Generate an npm token with publish permissions
143
+
2. Add the token as a GitHub repository secret named `NPM_TOKEN`
144
+
3. Update the version in package.json
145
+
4. Commit the changes and push to GitHub
146
+
5. Create a new tag for the release: `git tag v1.x.x && git push --tags`
147
+
6. Create a new release on GitHub using the tag to trigger the publishing workflow
148
+
149
+
The GitHub Actions workflow will use pnpm to build, test, and publish the package to the npm registry.
150
+
136
151
## Security
137
152
138
153
Nothing is perfectly secure, but I have tried to think through the security implications of running a helper like this. Here are some thoughts and I would definitely welcome any others in the issues or discussions sections:
0 commit comments