GitIgnore File for solidity

# Created by https://Shodkk.com/create-gitignore (Shantanu Bombatkar) SirDeploy Package # It helps deploy fakeserver ReactApp on Heroku and Github Pages # Hope it helps || Thanks for Using SirDeploy Package ### Solidity ### # Logs logs *.log npm-debug.log* yarn-debug.log* yarn-error.log* lerna-debug.log* .pnpm-debug.log* # Diagnostic reports (https://nodejs.org/api/report.html) report.[0-9]*.[0-9]*.[0-9]*.[0-9]*.json # Runtime data pids *.pid *.seed *.pid.lock # Directory for instrumented libs generated by jscoverage/JSCover lib-cov # Coverage directory used by tools like istanbul coverage *.lcov # nyc test coverage .nyc_output # Grunt intermediate storage (https://gruntjs.com/creating-plugins#storing-task-files) .grunt # Bower dependency directory (https://bower.io/) bower_components # node-waf configuration .lock-wscript # Compiled binary addons (https://nodejs.org/api/addons.html) build/Release # Dependency directories node_modules/ jspm_packages/ # Snowpack dependency directory (https://snowpack.dev/) web_modules/ # TypeScript cache *.tsbuildinfo # Optional npm cache directory .npm # Optional eslint cache .eslintcache # Optional stylelint cache .stylelintcache # Microbundle cache .rpt2_cache/ .rts2_cache_cjs/ .rts2_cache_es/ .rts2_cache_umd/ # Optional REPL history .node_repl_history # Output of 'npm pack' *.tgz # Yarn Integrity file .yarn-integrity # dotenv environment variable files .env .env.development.local .env.test.local .env.production.local .env.local # parcel-bundler cache (https://parceljs.org/) .cache .parcel-cache # Next.js build output .next out # Nuxt.js build / generate output .nuxt dist # Gatsby files .cache/ # Comment in the public line in if your project uses Gatsby and not Next.js # https://nextjs.org/blog/next-9-1#public-directory-support # public # vuepress build output .vuepress/dist # vuepress v2.x temp and cache directory .temp # Docusaurus cache and generated files .docusaurus # Serverless directories .serverless/ # FuseBox cache .fusebox/ # DynamoDB Local files .dynamodb/ # TernJS port file .tern-port # Stores VSCode versions used for testing VSCode extensions .vscode-test # yarn v2 .yarn/cache .yarn/unplugged .yarn/build-state.yml .yarn/install-state.gz .pnp.* # Star the Repo https://github.com/shaantanu9/SirDeploy # https://www.linkedin.com/in/shantanu-bombatkar/ # End of File

List Of Files and Folders That Get Ignored using this Gitignore code

Above Code Helps ignore following files from solidity Project

Logs

Diagnostic reports (https://nodejs.org/api/report.html)

Runtime data

Directory for instrumented libs generated by jscoverage/JSCover

Coverage directory used by tools like istanbul

nyc test coverage

Grunt intermediate storage (https://gruntjs.com/creating-plugins#storing-task-files)

Bower dependency directory (https://bower.io/)

node-waf configuration

Compiled binary addons (https://nodejs.org/api/addons.html)

Dependency directories

Snowpack dependency directory (https://snowpack.dev/)

TypeScript cache

Optional npm cache directory

Optional eslint cache

Optional stylelint cache

Microbundle cache

Optional REPL history

Output of 'npm pack'

Yarn Integrity file

dotenv environment variable files

parcel-bundler cache (https://parceljs.org/)

Next.js build output

Nuxt.js build / generate output

Gatsby files

Comment in the public line in if your project uses Gatsby and not Next.js

https://nextjs.org/blog/next-9-1#public-directory-support

public

vuepress build output

vuepress v2.x temp and cache directory

Docusaurus cache and generated files

Serverless directories

FuseBox cache

DynamoDB Local files

TernJS port file

Stores VSCode versions used for testing VSCode extensions

yarn v2

What is GitIgnore File?

GitIgnore is a file that tells Git which files or folders to ignore in a project. It is used to avoid committing unwanted files to a Git repository such as temporary files created by the editor vi or temporary build files. It is also used to avoid committing sensitive information such as passwords or API keys to a public repository.

How to Create GitIgnore File?

Creating getting a file is quite simple you just need to create a normal file you can use touch dot Gitignore or you can create it from VS code or any editor you are using or you can directly create from your explorer. Just create a file where you don't need to give the name to the file just use dot get ignore

How to Create GitIgnore File?

How to use GitIgnore File to Ignore Files?

To Use Gitignore File just paste the file downloaded file to the root of the github repo, no need to configure anything. Just paste the file and you are good to go. If the code is push first you can clear the cache of the git by using git rm -r --cached . and then push the code again.

How to use GitIgnore File to Ignore Folders?

There is simple rules to ignoring folders in Gitignore file. Just add the folder name in the gitignore file and you are good to go. If you want to ignore the folder and all the subfolders then you can use /foldername/ and if you want to ignore the folder and all the subfolders and files then you can use /foldername/*. for example if you want to ignore the node_modules folder and all the subfolders and files then you can use /node_modules/* and if you want to ignore the node_modules folder and all the subfolders then you can use /node_modules/

How to use GitIgnore File to Ignore Files and Folders?

To ignore files and folders in Gitignore file you can use the same rules as we have used to ignore the folders. Just add the file name or folder name in the gitignore file and you are good to go. If you want to ignore the folder and all the subfolders then you can use /foldername/ and if you want to ignore the folder and all the subfolders and files then you can use /foldername/*. for example if you want to ignore the node_modules folder and all the subfolders and files then you can use /node_modules/* and if you want to ignore the node_modules folder and all the subfolders then you can use /node_modules/

Why GitIgnore File not Working?

There are many reasons why Gitignore file is not working. The most common reason is that you have not added the file to the root of the github repo. If you have added the file to the root of the github repo then you can clear the cache of the git by using git rm -r --cached . and then push the code again. Or there are some rules for gitignore file to work properly. You can check the rules here.

Rules for GitIgnore File

There are some rules for gitignore file to work properly. You can check the rules here. To Avoid the Gitignore file not working you can follow the rules. Rule 1 The File that you already pushed on github you can't ignore it. Rule 2 Folder name should be in the gitignore file. Rule 3 If you want to ignore the folder and all the subfolders then you can use /foldername/ and if you want to ignore the folder and all the subfolders and files then you can use /foldername/*. for example if you want to ignore the node_modules folder and all the subfolders and files then you can use /node_modules/* and if you want to ignore the node_modules folder and all the subfolders then you can use /node_modules/ Rule 4 If you want to ignore the file then you can use the file name in the gitignore file. Rule 5 If you want to ignore the file and all the subfolders then you can use /filename/ and if you want to ignore the file and all the subfolders and files then you can use /filename/*. for example if you want to ignore the package-lock.json file and all the subfolders and files then you can use /package-lock.json/* and if you want to ignore the package-lock.json file and all the subfolders then you can use /package-lock.json/

GitIgnore File for solidity

Create a .gitignore file to tell git which files or folders to ignore in your solidity project.

List Of Files and Folders That Get Ignored using this Gitignore code

Create GitIgnore File

What is GitIgnore File?