.gitignore for Plone
16 ignore rules for Plone, ready to copy into your repository.
Content management system
The complete .gitignore for Plone
# Generated by LFGitignore - https://lfgitignore.com
# Created: 2026-08-05 01:30:04 UTC
# Technologies: Plone
### Plone ###
# Build output directory
build/
*.pyo
# Eclipse output directory
bin/
*.tmp*
# Compiled message catalogs
*.mo
# Python egg package
*.egg
# Distribution directory
dist/
*.egg-info
.*.cfg
*.pyc
# Python development eggs
develop-eggs/
# Downloaded files
downloads/
# Python egg packages
eggs/
fake-eggs/
# Buildout parts
parts/
var/
What these Plone rules actually ignore
Every pattern below, and why it belongs in your .gitignore.
General
| Pattern | What it ignores |
|---|---|
build/ |
Build output directory |
*.pyo |
General |
bin/ |
Eclipse output directory |
*.tmp* |
General |
*.mo |
Compiled message catalogs |
*.egg |
Python egg package |
dist/ |
Distribution directory |
*.egg-info |
General |
.*.cfg |
General |
*.pyc |
General |
develop-eggs/ |
Python development eggs |
downloads/ |
Downloaded files |
eggs/ |
Python egg packages |
fake-eggs/ |
General |
parts/ |
Buildout parts |
var/ |
General |
How to use this .gitignore for Plone
- Copy the Plone rules above, or download the file directly.
- Create a file named .gitignore at the root of your Git repository and paste the rules into it.
- If some of those files are already tracked, run git rm -r --cached . then commit again — Git only applies ignore rules to untracked files.
- Commit the .gitignore so everyone on the team shares the same rules.