borgbackup/borg

borg2 find?

Closed

#9,974 opened on Jul 30, 2026

View on GitHubContributor guide
 (0 comments) (1 reaction) (1 assignee)Python (732 forks)batch import
easygood first issuequestion

Repository metrics

Stars
 (10,086 stars)
PR merge metrics
 (Avg merge 5d 12h) (91 merged PRs in 30d)

Description

Do we need this?

It could support the usual archive matching options (--last, --match-archives, ...) and then iterate over the matching archives.

For each archive, it would iterate over all items and could match misc. search criteria (e.g.: pattern match on file path, ...) and then output archive name and item it found.

One can do something similar already by:

  • borg list (maybe also using custom --format) and grep
  • borg mount and find

So, would a borg find be worth it?

Note:

This would not use an index (because keeping an index up-to-date costs a lot of runtime and also likely quite a lot of space).

Contributor guide

Research direction
Explore Borg's existing command implementations (list, mount) and their options to assess whether a find command is needed and what it should do.
Tech stack
python
Domain
clisearch
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitPython
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
50