Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

Properly Support multi-project repos

未关闭
#4,199 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
28/100
Issue 类型
功能
描述清晰度
需要澄清
活跃度
活跃
技术栈
github-actions, typescript
领域
ci-cd

调研方向

Start from the linked example workflow (ebp-ci quarkus-ci-pipeline.yml, line 33) to see how a sub-project is currently selected, then trace which action inputs (init/analyze steps) control that selection and how results are aggregated before upload to code scanning. The payload gives no acceptance criteria, so the first deliverable is a maintainer-accepted design for per-sub-project separation rather than code; check for a response in the issue thread before starting.

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

描述

Hello, Came across the CodeQL action but it looks like I am not really able to use it effectively as I have a monorepo that has multiple sub-projects.

Main issues:

  1. While main syntax of the workflow is capable of being configured to focus on just one sub-project, it is cumbersome to do so.
  2. The integration with GitHub (at the project level) simply does not support the practice at all; does not separate per sub-project, but shows an aggregation of all projects

Any way we can get to where this is doable, or am I just not finding how to do this? Example of what I have going here: https://github.com/Epic-Breakfast-Productions/ebp-ci/blob/main/.github/workflows/quarkus-ci-pipeline.yml#L33

主要语言
TypeScript
星标
1.7k
派生
494
平均合并
1 天 10 小时
30 天内合并 PR
52

环境准备

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

github/codeql-action 的其他 Issue

查看 github/codeql-action 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

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