As a developer, the task of adding thousands of files or directories falls to you when the scope of your Magento project grows. That’s where the Git repository comes in. Git helps developers track all happenings within the modules and files that contain thousands of lines of code (LOC), so all the developers are on the same page.
But some minor changes might be overlooked when you’re going through these activities. How do you use Git to get around this?
For that, we use Magento gitignore. This is a .gitignore file with the Magento Open Source project repository.
What is Git?
Before I delve into an explanation of Magento 2 gitignore, Let’s quickly talk about Git. It’s an open-source control system that was built to help developers on all kinds of projects, from a static website to a gigantic complex ERP solution. It is an easy-to-learn, use, and master tool that helps every dev-team in their day-to-day operations.
Apart from that, if you are a Cloudways user, you can deploy code to your Magento application from your git repositories. Ensure that your git repository supports Git over SSH to get this task done.
Book a Personalized Cloudways Product Demo With One of Our Expert
The Purpose of Magento 2 Gitignore
Magento gitignore ensures that certain files remain untracked by Git.
If you want to stop tracking a file that was or is currently being tracked, use the command below:
git rm --cached
Also, the files that have already been tracked by Git are not affected.
Magento 2 Gitignore Pattern
Here are some helpful ways to understand the Magento 2 gitignore pattern:
- A blank line with no match files serves as a separator for readability.
- A line starting with # serves or represents a comment. Place a backslash () in front of the first # for the patterns that begin with a hash.
- By default, trailing spaces are ignored. It will be useless until you won’t use them with a backslash ().
- An optional prefix “!” negates the pattern. It helps add any matching file that was excluded by a previous pattern.*
*Please note, it is not possible to reinclude a file if a parent directory of that file is excluded or deleted. Git doesn’t mention excluded directories for performance issues. If you want to use it, here’s an example, “!footer!.txt”.
- The slash (/) is used as the directory separator. Separators occur at the beginning, middle, or end of the .gitignore search pattern.
- If you find the separator at the beginning or middle, the pattern is relative to the directory level.
- The separator at the end of the pattern only matches the directories.
For example, the pattern
This article was written by Abdur Rahman and originally published on The Official Cloudways Blog.