Make adr files recognition stricter #108
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This fix makes
adr listandadr linkwork properly when there are extraneous files along with adr files.I just changed
to
Explanation:
-maxdepth 1exclude subfolders; this is faster if you have subfolders with a lot of files, for instance images linked by your ADRs-type ffiles only^.{${#adr_dir}}skip as many chars as adr_dir length. This is more robust than matching the initial path with^$adr_dirbecause adr_dir might contain special regex chars that should be escaped at runtime.[0-9]*[1-9][0-9]*any sequence of digits other than all zeros (0 is not a valid adr; for instanceadr newstarts from 1)\.md$make sure the extension is exactly.md(for instance.md5files are excluded)