concourse / concourse/git-resource
Suggestion: "strict" mode for paths/ignore_paths options
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 203
- Forks
- 305
- Avg merge
- 11d 14h
- Merged PRs (30d)
- 2
Description
Problem: it's easy to make mistakes when limiting the scope of a git resource with the paths and ignore_paths options, inadvertently making use of files which aren't included by these lists. This can make life get very weird - especially so if you're using multiple git resources pointing at the same repo with different paths settings.
Partial solution: a "strict" mode which would actively strip the working tree of any files not included by these filters, so that attempted use of any of these files will fail.
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
The issue names the paths and ignore_paths options but no implementation files or tests. Start by locating where the git resource applies these filters and determine how a strict working tree should behave. Done means excluded files are stripped so attempts to use them fail without affecting included files.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git
- Domain
- devops
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100