Skip to content
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.

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

How to publish a public pack with codeql #18311

Open
trganda opened this issue Dec 18, 2024 · 1 comment
Open

How to publish a public pack with codeql #18311

trganda opened this issue Dec 18, 2024 · 1 comment
Labels
question Further information is requested

Comments

@trganda
Copy link

trganda commented Dec 18, 2024

I'm writing a custom library with codeql and try to publish it github container registry

$ 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?

@trganda trganda added the question Further information is requested label Dec 18, 2024
@mbg
Copy link
Member

mbg commented Dec 18, 2024

Hi @trganda,

Sorry, I don't believe it is possible to change the visibility of a package while uploading it with codeql pack publish.

You could try the method described in https://github.com/orgs/community/discussions/55094 to use the API to mark the package as public afterwards, but I haven't tested if this works.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants