Having a git repo inside the keybase file system private folder was not a good idea
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 9.2k
- Forks
- 1.3k
- Avg merge
- 12h 58m
- Merged PRs (30d)
- 56
Description
Love the idea of Keybase File System! What did not work so well was having a git repository to keep a history of my personal "journal" file. Too many updates by git internal manipulations made Keybase File System go a little nuts on my machine. So I'm posting this as a word of advice and warning; do not keep a git repository in a private Keybase Filesystem folder. At least not on Windows.
Keybase version: 1.0.17-20160822152935+692af12
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
No source files or tests are named. Start by reproducing the reported interaction between a Git repository and a private Keybase Filesystem folder on Windows, using the issue's Keybase version as context; done would require a confirmed cause and an agreed fix or documented limitation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git
- Domain
- operating-systems
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100