Do I need to commit .gitignore?

Yes — .gitignore should be committed to the repository so all collaborators benefit from the same ignore rules.

How do I add custom patterns?

Open your .gitignore file and add the pattern on a new line. Use # for comments, * for wildcards, / to match directories, and ! to un-ignore a previously ignored path.

How do I ignore a file that is already tracked?

Adding a file to .gitignore does not remove it from tracking if it was previously committed. Run: git rm --cached to stop tracking it without deleting the file locally.

Should I commit composer.lock?

Yes for applications — it ensures everyone installs identical package versions. For libraries, committing composer.lock is discouraged.

.gitignore for PHP

PHP Composer vendor directory, cache files, and environment configuration.

Quick presets

Selected (1)

PHP

Your selections never leave your browser. Generation happens entirely client-side.

Raw

12 patterns · 301 B

# Generated by DevZone Tools — https://devzone.tools/tools/gitignore-generator
# Templates: PHP
# 2026-04-20

# ---- PHP ----
# PHP
/vendor/
.env
.env.backup
.env.production
Homestead.json
Homestead.yaml
auth.json
npm-debug.log
yarn-error.log
.phpunit.result.cache
.php-cs-fixer.cache
.php_cs.cache

What this template ignores

Ignores the Composer vendor/ directory, .env secrets files, PHPUnit and PHP-CS-Fixer caches, and Laravel Homestead configuration.

Common additions

+storage/logs/ — Laravel log files
+bootstrap/cache/ — Laravel framework cache

Commonly paired with

laravel symfony composer Combine →

Frequently asked questions

Do I need to commit .gitignore?: Yes — .gitignore should be committed to the repository so all collaborators benefit from the same ignore rules.
How do I add custom patterns?: Open your .gitignore file and add the pattern on a new line. Use # for comments, * for wildcards, / to match directories, and ! to un-ignore a previously ignored path.
How do I ignore a file that is already tracked?: Adding a file to .gitignore does not remove it from tracking if it was previously committed. Run: git rm --cached <file> to stop tracking it without deleting the file locally.
Should I commit composer.lock?: Yes for applications — it ensures everyone installs identical package versions. For libraries, committing composer.lock is discouraged.

Looking for something else? Browse all templates →