Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Reasons for making this change:
I am a core contributor to the Aptos blockchain https://github.com/aptos-labs/aptos-core, and I've written enough Move contracts to be inconvenienced / copy the same .gitignore between each. Trying to make it as simple as possible for onboarding.
Move language is used for MoveVM based blockchains as the language native to them. The compiler provides a folder build/ that holds the build artifacts.
The .aptos/ folder is ignored so people do not upload their private keys to a git repository.
Links to documentation supporting these rule changes:
Here's the Move book, though, it looks like it doesn't explicitly say that this comes from the compiler.
Example:
This applies to all blockchains that use the Move compiler.
Additionally, for Aptos specifically the Aptos CLI adds an account it'll create a file structure like below where the config.yaml has credentials in it:
It's best that all Move blockchains add anything here that may add unwanted credentials associated with their blockchains.
If this is a new template: