You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When a backup branch is created a .bbinfo JSON file is created in the root of the repository directory.
Should this be committed to the main branch of the repository or should this be in .gitignore? How does the extension behave if the file is missing? How should we approach the file?
The text was updated successfully, but these errors were encountered:
So right now this depends on your use case, where if you're working with multiple devices, it's probably better for you to commit it by checking the git-backup-sync.shouldCommitBranchInfoFile setting, but if you only intend to work on one device adding it to .gitignore is probably the best.
Sorry it's generally a confusing artifact, I was thinking of getting rid of the bbinfo file completely recently. Or at least not using it by default. (It was to support custom backup branch names, but it went down a rabbit hole and caused more problems than it fixed lol)
When a backup branch is created a
.bbinfo
JSON file is created in the root of the repository directory.Should this be committed to the main branch of the repository or should this be in
.gitignore
? How does the extension behave if the file is missing? How should we approach the file?The text was updated successfully, but these errors were encountered: