Kyle Varga
My feedback
34 results found
-
6 votes
An error occurred while saving the comment -
2 votesKyle Varga
supported this idea
·
-
15 votes
An error occurred while saving the comment Kyle Varga
commented
Eric - Salesforce will remove quick deploy option (so Gearset would then fall back to full deployment). Right now we see a huge delay with:
1. Gearset validation
2. Salesforce validate-only deployment
3. Merge Request / Repo Merge
4. Full Salesforce Deploy.At minimum, quick deploy should be able to be used for the 4th step.
Kyle Varga
supported this idea
·
-
1 voteKyle Varga
shared this idea
·
-
33 votesKyle Varga
supported this idea
·
-
38 votesKyle Varga
supported this idea
·
-
4 votesKyle Varga
supported this idea
·
-
4 votesKyle Varga
supported this idea
·
-
1 voteKyle Varga
shared this idea
·
-
1 voteKyle Varga
shared this idea
·
-
1 voteKyle Varga
shared this idea
·
-
2 votesKyle Varga
supported this idea
·
-
2 votes0 comments · Help us improve Gearset » Integrations and connections (Jira, source control, DX etc.) · Admin →Kyle Varga
shared this idea
·
-
7 votesKyle Varga
shared this idea
·
-
3 votesKyle Varga
supported this idea
·
-
5 votesKyle Varga
supported this idea
·
-
2 votes
An error occurred while saving the comment Kyle Varga
commented
Agreed. This could be great. Even starting with something simple that can be detected like Inactive Workflow Rules, Process Builders, and Triggers could be a start. Further analysis like SymbolTable analysis to determine unused apex classes or methods would also be helpful.
Kyle Varga
supported this idea
·
-
3 votesKyle Varga
shared this idea
·
-
1 voteKyle Varga
shared this idea
·
-
1 voteKyle Varga
shared this idea
·
Issue I see with this is that without a force-push you cant remove that commit from history of release branch. We would want functionality to automate creating a new release branch and abandoning the old one. Vs abanoning the old one and re-creating (and having to stop a bunch of validations from re-running.