pin path ancestors?
Open
need/community-input
topic/commands
- Dominant language
- Go
- Stars
- 17.1k
- Forks
- 3.2k
- Avg merge
- 3d 18h
- Merged PRs (30d)
- 11
Description
when:
```
ipfs pin add -r foo/bar
```
foo is not pinned today. but it should be-- otherwise cannot access things
Contributor guide
Research direction
Start by running `ipfs pin add -r foo/bar` and trace the pin-add path for recursive directory arguments. Confirm how ancestor paths are handled, then verify that `foo` is pinned and remains accessible when the recursive pin completes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend, cli
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100