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
{{ message }}
This repository has been archived by the owner on Jun 11, 2019. It is now read-only.
I suppose this is almost expected behavior, but the .gitignore file that gets created in .dapple doesn't go along to the remote repo when I push a change. this matters because the git submodules that I created in .dapple/packagesdo get pushed to remote, which creates the .dapple folder remotely. this means that when I clone this repo elsewhere, a .dapple folder gets created with no .gitignore, which means the chain_db folder is listed as untracked. not sure if there is a good solution to this problem, but I wanted to make a note of it.
The text was updated successfully, but these errors were encountered:
thanks for the notice. I will address this soon.
Its probably the best choice to create a top level .gitignore with **/chain_db/** inside so it gets excluded everywhere
I suppose this is almost expected behavior, but the
.gitignore
file that gets created in.dapple
doesn't go along to the remote repo when I push a change. this matters because the git submodules that I created in.dapple/packages
do get pushed to remote, which creates the.dapple
folder remotely. this means that when I clone this repo elsewhere, a.dapple
folder gets created with no.gitignore
, which means thechain_db
folder is listed as untracked. not sure if there is a good solution to this problem, but I wanted to make a note of it.The text was updated successfully, but these errors were encountered: