Why does backup default to `steipete/backup-gog.git` rather than requiring a user-owned remote?

Open
#1,287 1 comment 1 reaction 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
18/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Active
Tech stack
git, go
Domain
cli, security

Research direction

Start with the default remote in internal/backup/config.go, then the push flag in internal/cmd/backup.go and the git push path in internal/backup/git.go. Before changing code, a maintainer needs to decide whether the default destination is intentional and whether pushing should require an explicitly configured remote. Done means that decision is recorded and, if it changes, backups stay local unless the user sets a remote.

Written by the indexing model from the issue text.

Description

clawsweeper:needs-product-decision clawsweeper:needs-security-review clawsweeper:no-new-fix-pr clawsweeper:source-repro impact:security issue-rating: 🦞 diamond lobster P2

In v0.47.1, the default backup configuration points to:

https://github.com/steipete/backup-gog.git

This default is also present on main when checked. The repository returns 404 for me, so I cannot determine whether it is private, deleted, or nonexistent.

The code enables pushing unless --no-push is supplied and contains a git push -u origin HEAD path.

Sources: default remote, push option, push implementation.

Could you clarify:

  • Why is a maintainer-account repository the default destination for users’ backups?
  • Is this an intentional shared destination or a development default left in the configuration?
  • Why not require an explicitly configured remote, with local-only backup otherwise?

I understand that the main backup payloads are encrypted. My question concerns the default destination and user control over outbound transfers.

This report is based on source inspection; I have not run a backup or established that any user data reached that repository.

Dominant language
Go
Stars
8.5k
Forks
721
Avg merge
17h 48m
Merged PRs (30d)
52

Getting set up

  • Ships a Dockerfile or Docker Compose file
  • No pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from openclaw/gogcli

All issues in openclaw/gogcli

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.