feat(review-action): project_dir input for monorepo dbt projects (avoid the --cwd CLI workaround)
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 72/100
- Issue type
- Feature
- Clarity
- Clearly specified
- Activity status
- Quiet
- Tech stack
- github-actions, typescript
Research direction
Start in the github/review composite action and trace how it invokes altimate review and resolves manifest_path. Add the project_dir or working_directory input so it maps to --cwd and manifest paths resolve from that directory; done means a monorepo dbt project can use the action directly and changed models are correlated correctly.
Written by the indexing model from the issue text.
Description
The composite GitHub Action (github/review) assumes the dbt project is at the repo root: it runs 'altimate review' from the job working dir and resolves the manifest relative to it. In a monorepo where the dbt project lives in a subdir (e.g. altimate-ingestion's packages/transform-snowflake/dbt), the action can't be used directly — we had to bypass the composite action and invoke the CLI in a run step with 'altimate review --cwd ' (see AltimateAI/altimate-ingestion #677/#678).
Ask: add a 'project_dir' (a.k.a. working_directory) input to the action that maps to 'altimate review --cwd <project_dir>', and resolve manifest_path relative to it, so monorepo repos can use the composite action directly. Validated end-to-end that --cwd correlates changed models correctly for a subdir project; this just surfaces it as a first-class action input.
- Dominant language
- TypeScript
- Stars
- 813
- Forks
- 134
- Avg merge
- 2d 5h
- Merged PRs (30d)
- 62
Contributor 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 AltimateAI/altimate-code
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
AltimateAI/altimate-code#1323 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
AltimateAI/altimate-code#1288 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 92/100
AltimateAI/altimate-code#1285 ·
-
privacy: Altimate Base consent dialog no longer discloses persistent per-installation identifier Open
Difficulty 1/5 Under an hour Newbie friendliness 88/100
AltimateAI/altimate-code#1284 ·
-
Difficulty 2/5 Under an hour Newbie friendliness 72/100
AltimateAI/altimate-code#1283 ·
All issues in AltimateAI/altimate-code
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
ontola/atomic-server#1625 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
melgarafael/DeskcommCRM#1451 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 82/100
-
bug via-triage
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
bot:ai-assisted component:compact-js status:untriaged
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
midnightntwrk/midnight-sdk#403 ·