Jonathan Flatt
My feedback
30 results found
-
6 votes
-
5 votes
-
3 votes
-
13 votes
-
4 votes
-
2 votes
An error occurred while saving the comment -
1 vote
-
15 votes
An error occurred while saving the comment 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.
-
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
-
6 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 →
-
1 voteStarted · 0 comments · Help us improve Gearset » Integrations and connections (Jira, source control, DX etc.) · Admin →
-
17 votes
-
5 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.
At least in bitbucket, loading the repositories on the compare and deploy page takes around 10 seconds. 99% of the time we'll be using only a single repository. Being able to set a default repository and perhaps on the page allow the user to change the repository and only then retrieve the repositories from VCS.