chore: remove nested .gitignores to solve yarn npm publish issue

It seems that having a .gitignore file might have an impact for `npm publish` (so I assume this might also be true for `yarn npm publish`. That could explain why current preview-builds does not include any code files!
MetaMask · Sep 4, 2024 · 37040eb · 37040eb
1 parent 35751c9
commit 37040eb
Show file tree

Hide file tree

Showing 7 changed files with 0 additions and 417 deletions.
diff --git a/.gitignore b/.gitignore
@@ -1,7 +1,6 @@
 .DS_Store
 dist/
 coverage/
-docs/
 
 # Logs
 logs

diff --git a/packages/keyring-api/.gitignore b/packages/keyring-api/.gitignore
diff --git a/packages/keyring-eth-hd/.gitignore b/packages/keyring-eth-hd/.gitignore
diff --git a/packages/keyring-eth-ledger-bridge/.gitignore b/packages/keyring-eth-ledger-bridge/.gitignore
diff --git a/packages/keyring-eth-simple/.gitignore b/packages/keyring-eth-simple/.gitignore
diff --git a/packages/keyring-eth-trezor/.gitignore b/packages/keyring-eth-trezor/.gitignore