Properly Support multi-project repos
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 28/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Active
- Tech stack
- github-actions, typescript
- Domain
- ci-cd
Research direction
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.
Written by the indexing model from the issue text.
Description
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:
- While main syntax of the workflow is capable of being configured to focus on just one sub-project, it is cumbersome to do so.
- 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
- Dominant language
- TypeScript
- Stars
- 1.7k
- Forks
- 494
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 52
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from github/codeql-action
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
github/codeql-action#4202 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
github/codeql-action#4052 · 4 comments ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
github/codeql-action#4185 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
github/codeql-action#4173 · 4 comments ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
github/codeql-action#4078 · 1 comment ·
Maintainers usually reply within 1 day
All issues in github/codeql-action
Similar issues
-
nextjs-tracking
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
cloudflare/vinext#3887 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
apache/rocketmq-dashboard#6331 ·
Maintainers usually reply within 5 days
-
bug cache clinical-safety P1-critical
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
juspay/blend-design-system#1788 ·
Maintainers usually reply within 1 day
-
[Analytics] Add Focus Time-Block Efficiency Ratio Calculator in src/lib/focus/efficiency-ratio.tsOpenanalytics beginner friendly community contributions-welcome enhancement good first issue hacktoberfest help wanted up-for-grabs
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day