Add a "posixfs scan" command for scanning the posix tree for new files

[aduffeck]

/cc @butonic

[codacy-production]

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

🟢 Metrics 11 complexity · 0 duplication

Metric	Results
Complexity	11
Duplication	0

View in Codacy

🟢 Coverage 0.00% diff coverage · 0.00% coverage variation

Metric	Results
Coverage variation	✅ 0.00% coverage variation (-1.00%)
Diff coverage	✅ 0.00% diff coverage

View coverage diff in Codacy

Coverage variation details

	Coverable lines	Covered lines	Coverage
Common ancestor commit (734fd74)	81228	18655	22.97%
Head commit (9de4e24)	81281 (+53)	18667 (+12)	22.97% (0.00%)

Coverage variation is the difference between the coverage for the head and common ancestor commits of the pull request branch: <coverage of head commit> - <coverage of common ancestor commit>

Diff coverage details

	Coverable lines	Covered lines	Diff coverage
Pull request (#2789)	53	0	0.00%

Diff coverage is the percentage of lines that are covered by tests out of the coverable lines that the pull request added or modified: <covered lines added or modified>/<coverable lines added or modified> * 100%

_{NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.}

[dschmidt]

Maybe worth cross linking documentation between search index --force-rescan and this?
Explaining which is good for what and why and when I might need one or the other or both?

[aduffeck]

Maybe worth cross linking documentation between search index --force-rescan and this? Explaining which is good for what and why and when I might need one or the other or both?

That's a good point. While the search index --force-rescan is documented in the service README.me and thus ends up in the documentation the maintenance commands are currently missing completely as far as I know. @Svanvith Is that something we could add?