vbatts/quay
Archived
1
0
Fork 0
Code Issues Pull requests Releases Wiki Activity

Add clear instructions to the github trigger setup on how to authorize additional organizations

Browse source 
Until now, this has been quite hard for customers to find
This commit is contained in:
Joseph Schorr 2018-09-27 15:59:00 -04:00
parent b894d8e58c
commit 1f8e0b72be
3 changed files with 26 additions and 3 deletions
Download patch file Download diff file Expand all files Collapse all files

4
static/js/directives/ui/manage-trigger/manage-trigger.component.html
View file

@ -61,8 +61,8 @@
<p>
<span class="registry-name"></span> has been granted access to read and view these {{ $ctrl.namespaceTitle }}s.
</p>
<p>
Don't see an expected {{ $ctrl.namespaceTitle }} here? Please make sure third-party access is enabled for <span class="registry-name"></span> under that {{ $ctrl.namespaceTitle }}.
<p class="co-alert co-alert-info gh-grant-message" ng-if="$ctrl.githost == 'github'">
<b>Don't see an expected organization here?</b>Please visit <a href="{{ $ctrl.githubTriggerEndpoint }}settings/connections/applications/{{ $ctrl.githubTriggerClientId }}" target="_blank" rel="nofollow noopener">Connections with <span class="registry-name"></span></a> and choose <span class="gh-button">Grant</span> or <span class="gh-button">Request</span> before reloading this page.
</p>
</div>
</linear-workflow-section><!-- /Section: Namespace -->