Commit graph

9 commits

Author SHA1 Message Date
Joseph Schorr
8bbe0e5e9b Always allow robot accounts to be selected by admins in trigger setup
Currently during trigger setup, if we don't know for sure that a robot account is necessary, we don't show the option to select one. This fails if the user has a Dockerfile in a branch or tag with a private base image *or* they *intend* to add a private base image once the trigger is setup. Following this change, we always show the option to select a robot account, even if it isn't determined to be strictly necessary.
2017-03-20 13:24:55 -04:00
alecmerdler
52b2f5828c fix no robot accounts visible 2017-03-08 15:27:22 -08:00
alecmerdler
f7258c85e4 fix styling for deselected organizations in build trigger setup 2017-03-07 11:27:52 -08:00
Joseph Schorr
5a2a72bfac Fix padding in mobile view of triggers
Fixes https://www.pivotaltracker.com/story/show/141245867
2017-03-07 14:11:37 -05:00
Joseph Schorr
f2750ba645 Make sure to initialize trigger setup when *both* values change
Hopefully fixes https://www.pivotaltracker.com/story/show/141245817
2017-03-07 14:05:55 -05:00
alecmerdler
8fcd76c0be removed old templates 2017-02-28 16:51:44 -05:00
alecmerdler
e59d394491 refactoring linear workflow directives 2017-02-28 16:51:43 -05:00
alecmerdler
b1516193a5 converted ManageTriggerGithostComponent to TypeScript 2017-02-28 16:51:43 -05:00
alecmerdler
14222be9fe working on ManageTriggerGithostComponent 2017-02-28 16:51:43 -05:00