github / github/codeql

When publishing a codeql query pack with the --allow-prerelease option, if the version already exists, it should be overwritten

未关闭
#13,686 1 条评论 1 个 reaction 已指派 0 人 在 GitHub 查看
backlog enhancement
主要语言
CodeQL
星标
10.1k
派生
2.1k
平均合并
2 天 15 小时
30 天内合并 PR
141

描述

# Description

I am working on a custom query pack which I am publishing under my own account. This query pack is for the Vert.X Java framework (for more details, you can check #12844 ) and we will contribute it back to CodeQL once we have a more decent amount of queries. For the moment this is a separate query pack.

While this under heavy development and has no official released version, I am using a semver version such as `1.0.0-alpha`, as advised by @aeisenberg , who also suggested using the `--allow-prerelease` option. I was under the impression that when I execute:

```
codeql pack publish --github-auth-stdin --allow-prerelease
```

this would also overwrite the existing package, but this does not appear to be the case.

In my opinion, this option should be further extended to overwrite packages.

Deleting the versions manually Is a cumbersome process, especially, if you have no other versions, because it means you have to remove the package and then recreate it. This means you also have to manually make it publicly accessible. Every time.

I also think that there needs to be a version format that is treated as a snapshot for which this will be done automatically. For example, in the Java world, in Maven / Gradle, there's the concept that versions ending in `-SNAPSHOT` are (clearly) snapshots. Could, perhaps, versions such as `1.0.0-snapshot` be automatically treated as snapshots that will always be overwritten by default, instead of even having to pass in a parameter like this?

贡献指南

打开贡献指南

调研方向

从 `codeql pack publish` 的实现入手,重点关注 `--allow-prerelease` 如何处理现有版本。明确完成后的行为是否应仅覆盖 prerelease 版本,还是还应引入自动 snapshot 处理,然后验证发布一个现有的 prerelease pack 是否会在无需手动删除的情况下产生约定的结果。

由索引模型根据 Issue 内容生成。

评估

领域
cli, devtools
Issue 类型
功能
难度
5/5
预计耗时
一周以上
活跃度
停滞
描述清晰度
基本清楚
新手友好度
25/100

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。