Make backup excluded directories configurable and extensible
NousResearch/hermes-agent · cluster 16988 · hermes cli
Data as of
3 open items. Fix attempted, not merged.
The short answer
2open issues
1open PR
6items grouped
- Known?
- Yes. 6 related items grouped here, 1 issue already closed.
- Fix event
- No fix has been merged to main. 2 PRs closed without merging; see the attempts below.
- Tracker
- The maintainers' tracker marks this
unresolved. That is separate from the fix event. - Still open
- 2 issues and 1 PR.
Next step: read the attempts below. Your case may extend or revive that work.
Pick up a Lab taskThese issues and PRs address hardcoded backup exclusion lists in hermes backup, specifically requesting that excluded directories be externalized and user-configurable, with Git for Windows installation cited as a concrete example of an unwanted inclusion.
Open issues2
Open PRs1
- PR#44859fix(backup): exclude Git for Windows installation from hermes backup
2 PRs closed without merging
From the close comments: superseded by another PR 1 · other 1
Closed issues · 1
- Closed#28970Feature Request: Make hermes backup exclusions configurable
How this cluster was grouped
-
Link evidence (
partly structural links): some members are connected by structural evidence (shared changed files, or a closing/superseded reference); the rest are joined by an automated relevance judgement over their text. - Members outside that structural core may belong to a different underlying problem.
-
Pairwise link density
0.25: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36.1.00means every pair is linked.
Pick up a Lab task
Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.
Open the LabAt a glance
- Subsystem
- hermes cli
- Closed issues
- 1
- Attempts
- 2 PRs closed without merging