Jonathan Flatt
My feedback
42 results found
-
1 vote
-
22 votes
An error occurred while saving the comment -
to add an option to not to run unit tests validation in CI job in case there are no changes detected
2 votes -
2 votes
An error occurred while saving the comment It would be nice to have a revert option in Gearset that wouldn't open a PR to the next environment.
-
7 votes
-
2 votes
-
6 votes
-
7 votes
An error occurred while saving the comment Would be very useful. When releases get large it's quite cumbersome to abandon a release and re-create.
-
3 votes1 comment · Help us improve Gearset » Integrations and connections (Jira, source control, DX etc.) · Admin →
An error occurred while saving the comment This would be fantastic. I'd like to manually review anything the Cleaner does before actioning. We have lots of managed packages and when testing found the repo cleaner to be too aggressive.
-
2 votes0 comments · Help us improve Gearset » Integrations and connections (Jira, source control, DX etc.) · Admin →
-
20 votes
-
6 votes
-
10 votes1 comment · Help us improve Gearset » Integrations and connections (Jira, source control, DX etc.) · Admin →
An error occurred while saving the comment This but for all supported VCSs would be very useful.
-
11 votes
-
2 votes
-
1 vote
-
2 votes
An error occurred while saving the comment Gearset seems to run too many redundant validations. In highly governed orgs where we want to run all unit tests with our deployments/validations this becomes very problematic and impractical as our unit tests can take up to four hours to run.
-
3 votes
-
6 votes
An error occurred while saving the comment I'd like this except the ability to tie it to a feature branch that runs when those promotion branches are merged.
-
3 votes
Agree with Jason's comment on bypassing the promotion pre-validation option in the CI job settings. It would save a considerable amount of time in busy orgs.