Ethereum Stack Exchange is a question and answer site for users of Ethereum, the decentralized application platform and smart contract enabled blockchain. It only takes a minute to sign up.
Sign up to join this community
I'm using the latest Truffle. Very nice, after having to roll my own dev environment in early 2016! But there is no obvious documentation as to what parts of the project need to be checked into Github.
For example, I'm unsure if the build directory needs to be checked in. I think the answer is 'yes' because one would want to remember what the format of the contracts that have been deployed, but I'm unsure.
This is the one I'm using rite now. I believe it may be helpful.
>$ cat .gitignore
contracts/.placeholder
test/.placeholder
build
node_modules
.gitignore? Standard practice is to commit it stackoverflow.com/questions/5765645/…
Oct 22, 2019 at 22:17
Consensys published an example project and it only has a key file which of course you shouldn't commit and node_modules.
deploy_mnemonic.key
node_modules
The answer probably should be - you MUST check in your build directory once you've deployed, because it caches the addresses of your contracts, which is absolutely critical to the truffle deployment system!
so:
>$ cat .gitignore
contracts/.placeholder
test/.placeholder
node_modules
.gitignore? Standard practice is to commit it stackoverflow.com/questions/5765645/…
Oct 22, 2019 at 22:17
You could use one of the .gitignore on some well-known ethereum projects on GitHub. Try this: OpenZeppelin's gitignore.
I have never used truffle, but my view (and the general rule as I understand) when it comes to source control is that you commit any files and folders that you want to track that can not be recreated.
You should not commit the build directory because the built files can be.. rebuilt. Storing that data would be an unnecessary use of space/bandwidth.
It also necessitates good practices. For example you can build your code, and then modify the source (from which those files are built). If you submitted everything to source control (without rebuilding), another team member might check it out and work with the built files which in this case are not fully up to date.
A brief look at their website implies that this build folder holds compiled contracts. I would not call that a build, but hey-ho :)
In my opinion you would be best served submitting everything to source control except the build folder.
The answers here are good.
Independent from wich project you are wokring on, I would add .DS_Store to any .gitignore file.
It's a file used in MacOS for directory settings. So even if you are not using Mac, I would add it. You never know. Maybe you collaborate with a Mac user some day.
