Skip to content

Patrick Fordey

← Gearset

My feedback

1 result found

  1. Ability to choose whether or not to respect the forceignore file

    4 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    1 comment  ·  Help us improve Gearset » Comparisons and difference visualization  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    An error occurred while saving the comment
    Patrick Fordey commented  · 

    This would be extremely helpful for a number of use cases where you want to be able to use files in source control for certain deployments but not others. The alternative right now is to keep either have two version of forceignore and keep moving back and forth depending on what you are doing or have two versions in two different branches you have to maintain. The alternative is to have two repos that has the metadata you want to deploy manually using Gearset.

    We have multiple use cases where we want to do post non managed packaged deployments to an org for certain metadata types that are not fully supported by packaging or are difficult to manage in packaging e.g. permission set groups.

    Patrick Fordey supported this idea  · 

Feedback and Knowledge Base

(thinking…)