Add file entries to the gitignore file in Git
This tutorial will discuss adding file entries to files in Git .gitignore
.
.gitignore
Add a file entry to a file
in Git
Git tracks changes to all files in the project directory of the Git repository. We may want to disable tracking of specific files in the Git repository.
Typically, files that we wish to ignore from tracing are those created as part of the build process, temporary files, or system-generated files.
Some common file types that are often ignored when tracking in Git repositories are as follows:
-
Code files created during compilation, such as
.o
, ,.pyc
or.class
; -
The output directory of the build, for example
/bin
,/out
or/target
; -
Runtime generated files, such as
.log
, ,.lock
or.tmp
; -
Hidden system files such as
.DS_Store
orThumbs.db
; -
Configuration files for personal IDEs, for example
.idea/workspace.xml
; -
Editor temporary files, such as
.swp
or.swo
(generated by the Vim editor); -
Package files or compressed files, such as
.jar
,.war
,.nar
,.zip
,.tar
,.gz
or.rar
.
We can use Git's .gitignore
file feature to ignore tracking of a file. It is a special file that is usually checked in at the root of the project directory in the Git repository.
There is no special command to trigger the ignore process. Whenever we have new files that we wish to ignore, we need to update .gitignore
the ./install/ignore/file and commit it to the repository.
We need to add patterns in the file that match the file names in the Git repository .gitignore
to decide whether to add or ignore them.
Following are .gitignore
the wildcard patterns used to match file names.
-
.log
Ignore.log
log files with extensions in directories, e.g. debug.log, .log, logs/debug.log -
/bin
Ignorebin
Folder -
.class
Ignore compiled class files -
.tmp
Ignoretmp
(temporary) files -
logs
logs
Ignore the contents of files and directories named .
By convention, we can place .gitignore
files in the top-level directory of the repository. We can also add multiple files in subdirectories .gitignore
.
.gitignore
Patterns in
a particular file are tested relative to the directory containing the file.
See .gitignore
an excerpt from the example file below.
$ cat .gitignore
# ignore the bin folders
**/bin/
# Compiled class file
*.class
# Log file
*.log
# tmp files
*.tmp
# Vim temp files
*.swp
*.swo
...
Add a #
comment to the file.
We can also add personal ignore patterns in local system repository. We need to add them to git/info/exclude
a specific file in the location in local system.
This is not version controlled, nor is it committed and distributed with our repository.
We can also define global Git ignore patterns for all repositories present in the local system. We need to set Git global properties core.excludesFile
.
So, for example, we can add the global ./opt/opt/ssl.sh file in our home directory .gitignore
and git config
configure its location using the ./opt/ssl.sh command as shown below.
$ touch ~/.gitignore
$ git config --global core.excludesFile ~/.gitignore
We have learned how to add file entries to .gitignore
files in Git.
For reprinting, please send an email to 1244347461@qq.com for approval. After obtaining the author's consent, kindly include the source as a link.
Related Articles
Git installation and establishment of local warehouse service
Publish Date:2025/04/05 Views:89 Category:Git
-
Git is a distributed version control system: the client does not only extract the latest version of the file snapshot, but also completely mirrors the original code repository. It has the following advantages: a. Since every extraction oper
git remote operation——multiple remote repositories for one project
Publish Date:2025/04/05 Views:131 Category:Git
-
Multiple remote repositories for a git project In our git project, the command to operate the remote repository information is $ git remote # 查看当前所有的远程仓库的名称 $ git remote -v # 查看远程仓库的名称和远程仓
Git cherry pick command usage
Publish Date:2025/04/05 Views:190 Category:Git
-
git cherry-pick is a powerful command that allows us to select an arbitrary Git commit by reference and attach it to the HEAD of the current working branch. Cherry picking is the act of picking a commit from one branch and applying it to an
Comparison between Git merge and Git rebase
Publish Date:2025/04/05 Views:171 Category:Git
-
The git rebase command may seem like Git wizardry to beginners, but if used carefully, it can actually make life easier for your development team. In this article, we compare git rebase with the related git merge command and identify all th
How to fix Git error Error: src refspec master does not match any
Publish Date:2025/04/05 Views:124 Category:Git
-
When using Git, we may encounter the error "src refspace master does not match any". Here's what the error means and how to fix it. What does src refspec master does not match any Mean in Git mean? We may encounter this error when we try to
Rebase local branch when pulling changes from remote repository branch in Git
Publish Date:2025/04/05 Views:144 Category:Git
-
This article will cover the basics of rebasing your local branch when pulling changes from a remote repository branch in Git. We use the version control system Git to track changes made to files. We commit changes in a local branch in our l
Undo Git Stash
Publish Date:2025/04/04 Views:187 Category:Git
-
This article explains how to make and save changes to a repository. Git allows you to save changes locally and push them to a server when needed. In Git, we don't use the term save , but commit . We use git add , git commit , and git stash
View a list of cache entries in Git
Publish Date:2025/04/04 Views:59 Category:Git
-
We often need to pause our work and focus on something else in our development environment. Therefore, we may need to temporarily save our current work and focus on a different one. We may want to resume our original work later. git stash T
Git stores specific files
Publish Date:2025/04/04 Views:115 Category:Git
-
This article will cover storing changes to only specific files in Git. In Git, when we make some changes in our working tree, we may have some changes which may or may not be staged in our local repo. We may now wish to save these changes f