new git-variables break leeway when using git-submodules
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 183
- Forks
- 27
- PR merge metrics
- No merged PRs in 30d
Description
Example: In https://github.com/gitpod-com/postman/issues/1, we get
$ leeway collect
FATA[0000] cannot resolve builtin variables test:docker: package sources are not within a Git working copy
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.
Research direction
Start by reproducing the reported leeway collect failure from the gitpod-com/postman example, focusing on builtin-variable resolution and the Git working-copy check when package sources use git submodules. Trace the collect entry point and identify how submodule paths are handled. Done means the command resolves the variables successfully for that layout and the regression is covered by a test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100