Skip to content

docs: clarify OIDC vs PAT publishing in README - W-24756661 #211

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
madhur310 wants to merge 1 commit into
base: main
Choose a base branch
from
Open

docs: clarify OIDC vs PAT publishing in README - W-24756661 #211

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -491,7 +491,7 @@ Before using these workflows, ensure your repository has:

1. **Required Secrets** (configured as GitHub Actions secrets):
- `IDEE_GH_TOKEN` - Personal Access Token with repo permissions for creating releases and pushing tags
- `VSCE_PERSONAL_ACCESS_TOKEN` - VS Code Marketplace Personal Access Token ([create one](https://code.visualstudio.com/api/working-with-extensions/publishing-extension#get-a-personal-access-token))
- `VSCE_PERSONAL_ACCESS_TOKEN` - VS Code Marketplace Personal Access Token for PAT-based publishing (not needed with OIDC; [create one](https://code.visualstudio.com/api/working-with-extensions/publishing-extension#get-a-personal-access-token))
- `IDEE_OVSX_PAT` - Open VSX Personal Access Token ([create one](https://open-vsx.org/user-settings/tokens))

2. **Repository Structure**:
Expand Down Expand Up @@ -795,7 +795,7 @@ jobs:
dry-run: true # Download and inspect without publishing
```

This requires a Trusted Publishing policy registered for the calling repo + this exact workflow filename on the Marketplace publisher management page.
This requires a Trusted Publishing policy registered for the calling repo + the calling workflow's filename (e.g., `publishVSCode.yml`) on the Marketplace publisher management page.

### openvsx-publish-release-vsix

Expand Down
Loading