Extend `vet` so that it produces a warning if any .gitignore files are in the srcs input to a package.
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 183
- Forks
- 27
- PR merge metrics
- No merged PRs in 30d
Description
Is your feature request related to a problem? Please describe
- It's normal to add build artefacts to
.gitignore - Leeways'
srcsglobs makes it easy to include unintended files
Describe the behaviour you'd like
I'd like for vet to provide a warning if any files that are .gitignored are part of the expanded srcs.
Describe alternatives you've considered
Today you can probably manually check for this using a combination of leeway describe, jq and a bit of bash.
Additional context
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 with the vet command and the code that expands package srcs globs; the payload does not name specific files or tests. Trace how .gitignore files are identified, then verify that vet warns when an ignored file appears in the expanded srcs and remains quiet otherwise.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- build-system, cli
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100