git push --force-with-lease always fails
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 9.2k
- Forks
- 1.3k
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 56
Description
When using a private Keybase git repository, git push --force-with-lease fails every time.
Initializing Keybase... done.
Syncing with Keybase... done.
To keybase://private/eridius/myrepo
! [remote rejected] master -> master (some refs were not updated)
This happens even though my remote-tracking branch is definitely up-to-date. Running git push --force instead works.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the failure against a private Keybase git repository with git push --force-with-lease, then compare it with the successful git push --force behavior. Trace the Keybase git remote handling, using the reported rejection and force-with-lease operation as entry points; done means an up-to-date remote-tracking branch no longer causes this rejection.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, go
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100