When retrieving changes from your development environment, you likely have files or metadata types that you want to exclude from committing to the source control repository. You can exclude individual files or all files in a specific directory with a .forceignore file. DevOps Center provides you the ability to view information about these ignored files but they don’t show up in the changes list.
If the project repository was created using the provided repository template, your project already includes a .forceignore file. This file was likely modified to ensure it contains all the files and metadata types your team wants to exclude when pulling changes from its development environments. If the project was created using Salesforce CLI or some other method, we recommend that you check this file into the source control system.
If you’re familiar with using Salesforce CLI outside of DevOps Center, we honor excluding
metadata when running any of the commands to deploy or retrieve metadata, such as sf project deploy start or sf
project retrieve start.
Some common files and metadata that are often excluded:
- package.xml
- Profiles
- App menu and app switcher
- Settings
- Object translations
- LWC configuration files
- Tests
See Salesforce Help: Determine What Metadata Types to Ignore During Development for sample syntax and considerations when updating the .forceignore file.