Add to .forceignore available in Metadata API project although it doesn't work there

Issue #2258 resolved
René Görgens created an issue

Hi Scott,

I’m watching your video about IC2 .forceignore Enhancements. Both in the 2.2.4.5 release notes and in the video, it is clearly stated that .forceignore only applies to source format projects.

  • I’m however seeing the Add to .forceignore menu option appearing for a Metadata API project where it has no effect. Even if I add a .forceignore file manually to the source root, nothing happens when selecting the menu option on a folder/file.

Other observations regarding .forceignore:

  • Question:

    • Wouldn’t the metadata filtering capabilities in Select Retrieval Scope (not to mention actual deploy/retrieve) also be beneficial for Metadata API projects?

Comments (4)

  1. Scott Wells repo owner

    Committed a change to remove these actions in metadata format projects. I’m not planning to add .forceignore support to those projects because it could lead to confusion as to whether that file is used when non-IC2 deployments and retrievals occur, e.g., via the Force Migration Toolkit (i.e., ant). The IC2 support is meant to complement the CLI’s own support in source format projects.

  2. Log in to comment