before we were setting the location on the window when we should have been just using Angular $location service instead
[TESTING -> tested locally with docker compose and a complete build]
- [ ] It works!
- [ ] Comments provide sufficient explanations for the next contributor
- [ ] Tests cover changes and corner cases
- [ ] Follows Quay syntax patterns and format
not sure what happened to the init from before
[testing -> tested locally with docker build]
- [ ] It works!
- [ ] Comments provide sufficient explanations for the next contributor
- [ ] Tests cover changes and corner cases
- [ ] Follows Quay syntax patterns and format
added subscope to prevent clobbering of robots
[testing -> tested locally with dockerfile build]
- [ ] It works!
- [ ] Comments provide sufficient explanations for the next contributor
- [ ] Tests cover changes and corner cases
- [ ] Follows Quay syntax patterns and format
* Add flag to enable trust per repo
* Add api for enabling/disabling trust
* Add new LogEntryKind for changing repo trust settings
Also add tests for repo trust api
* Add `set_trust` method to repository
* Expose new logkind to UI
* Fix registry tests
* Rebase migrations and regen test.db
* Raise downstreamissue if trust metadata can't be removed
* Refactor change_repo_trust
* Add show_if to change_repo_trust endpoint
* starting UtilService refactor
* pre find-replace angular.module('quay') => angular.module('QuayModule')
* successfully switched to ng-metadata for backported Angular2 API
* working with parent component reference in child
* fixing @Output to use EventEmitter
* fixed @Output events for custom git trigger
* more fixes
* refactored QuayPages module for backwards-compatibility
* reinitialized test.db
* use minified libraries
* replaced references for angular-ts-decorators
* fixed ng-show
Take ownership code got moved into its own directive in Oct, but we forgot we have a call in superuser panel for orgs as well. Fix this, and simplify the call sites
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.
