.gitignore: A file that tells Git which files or folders not to track, such as build output, local settings or secret keys.
Example
You add node_modules/ and .env to .gitignore so they are never committed.
Why .gitignore matters for IT interns
It stops you from accidentally committing huge folders or passwords — a common beginner mistake.
Where you will hear it
You will use this term almost daily when working on code with a team, through Git, GitHub, or a similar tool. If someone uses it and you are not sure what they mean in your project, it is completely fine to ask; every team uses terms a little differently.
Related terms
- Branch: A separate line of work in a repository, so you can make changes without affecting the main code until they…
- Clone: Downloading a full copy of a remote repository, including its history, to your own computer.
- Commit: A saved snapshot of your changes in Git, with a short message describing what you changed.
- Feature Branch: A branch created for one specific feature, fix or task.
- Fork: Your own copy of someone else’s repository on GitHub or a similar service, which you can change without…
- Git: The tool most software teams use to keep track of every change made to the code.
Next term: Acceptance Criteria
Related guides
Frequently asked questions
What is .gitignore?
A file that tells Git which files or folders not to track, such as build output, local settings or secret keys.
What is an example of .gitignore?
You add node_modules/ and .env to .gitignore so they are never committed.
Why does .gitignore matter for IT interns?
It stops you from accidentally committing huge folders or passwords — a common beginner mistake.
Explore more internship terms
The IT Internship Glossary explains 199 terms you will hear before and during your internship, with simple definitions and real examples.
Browse all 199 terms