.gitignore for Swift

Swift build artifacts, .swiftpm directory, and DerivedData.

Quick presets

Selected (1)
Swift
Your selections never leave your browser. Generation happens entirely client-side.
Raw

8 patterns · 233 B

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

# ---- Swift ----
# Swift
.DS_Store
/.build
/Packages
/Package.resolved
/*.xcodeproj
xcuserdata/
DerivedData/
.swiftpm

What this template ignores

Ignores Swift Package Manager build artifacts (.build/, .swiftpm/), resolved package pins (Package.resolved), and Xcode user data.

Common additions

  • +Pods/ — CocoaPods if not committing dependencies

Commonly paired with

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 Package.resolved?
For apps: yes, commit Package.resolved to lock dependency versions. For packages/libraries: it is optional.

Looking for something else? Browse all templates →