How to publish a public pack with codeql
- Vorherrschende Sprache
- CodeQL
- Sterne
- 10.1k
- Forks
- 2.1k
- Ø Merge
- 2 T. 15 Std.
- Gemergte PRs (30 T.)
- 141
Beschreibung
I'm writing a custom library with codeql and try to publish it github container registry
```bash
$ codeql pack publish --github-auth-stdin
Enter value for --github-auth-stdin (Authenticate to the github.com Container registry by passing a github.com GitHub Apps token or personal access token via standard input.):
Running on packs: trganda/java-utils.
Bundling and then publishing qlpack located at '/Users/trganda/Research/vscode-codeql/java-utils'.
Bundled qlpack created at '/var/folders/zq/bnfkv60s36z0lqyt0csfv68m0000gn/T/codeql-packaging6758600027471734602/.cache/java-utils.0.0.1.tgz'.
Packaging> Package 'trganda/java-utils@0.0.1' will be published to registry 'https://ghcr.io/v2/' as 'trganda/java-utils'.
Packaging> Package 'trganda/java-utils@0.0.1' will be published locally to /Users/trganda/.codeql/packages/trganda/java-utils/0.0.1
Publish successful.
```
The package was successful published but with private visibility default. And If I want to make this pack public, I need to config it in my profile.
Is there any arguments of codeql or other methods that can make the publish as public?
Beitragsleitfaden
Rechercherichtung
Start with the documented `codeql pack publish --github-auth-stdin` command and GitHub Container Registry visibility settings. Clarify whether the publish command supports public visibility or whether it must be changed in the package profile, then document the supported workflow and expected result.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Bewertung
- Tech-Stack
- github
- Bereich
- cli, security
- Issue-Typ
- Dokumentation
- Schwierigkeit
- 2/5
- Geschätzter Aufwand
- 1-3 Stunden
- Aktivitätsstatus
- Veraltet
- Klarheit
- Muss geklärt werden
- Anfängerfreundlichkeit
- 35/100