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
I have a small script in my .bashrc file that shows the current branch in the command prompt. Thus, every time a prompt is generated, dolt branch --show-current is run. This takes about 60 seconds for a database the size of the housing bounty database (~100GB ?). Thus, whenever this database is in a sub-directory, working on the command line becomes a PITA.
As a quick fix, I'm wondering if dolt needs to be fully initialized for every command. Could this be bypassed for things like branch, which really doesn't make sense to even run outside the database directory?
The text was updated successfully, but these errors were encountered:
i'd like to revisit this, it's so useful knowing what branch you're on by looking at the command prompt, but when the database is large it really becomes a painfully slow
is there some other way to get the current branch, like from the repo_state.json file
I have a small script in my .bashrc file that shows the current branch in the command prompt. Thus, every time a prompt is generated,
dolt branch --show-current
is run. This takes about 60 seconds for a database the size of the housing bounty database (~100GB ?). Thus, whenever this database is in a sub-directory, working on the command line becomes a PITA.As a quick fix, I'm wondering if dolt needs to be fully initialized for every command. Could this be bypassed for things like branch, which really doesn't make sense to even run outside the database directory?
The text was updated successfully, but these errors were encountered: