Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Refactor bbinfo file to be an advanced feature not enabled by default. #30

Merged
merged 1 commit into from
Apr 2, 2024

Conversation

maxyu1115
Copy link
Owner

As brought up here: #25

The branch info file has honestly been a rabbit hole I went down. The original idea was to have a solution solving the use case of having custom backup branch names. "If we don't have a config file, how will the extension know?" This lead to the branch info file, and then in order to make the branch info file work, I kept needing to add more and more jank settings, like shouldCommitBranchInfoFile, #20 , #22 , etc. After taking a step back from active development, it became embarrassingly obvious how hard to use and confusing this file was.

Instead, make the default behavior backup any branch A to gbs-backup-A. This should be enough for 99% of the users. For the remaining 1%, they can still enable the branch info file as an advanced setting.

@maxyu1115 maxyu1115 requested a review from mmmyr February 2, 2024 07:41
@maxyu1115 maxyu1115 merged commit 79b5bc6 into main Apr 2, 2024
@maxyu1115 maxyu1115 deleted the refactor-bbinfo branch April 2, 2024 06:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant