travis-web/assets/scripts/app/templates/repos/show/tools.hbs
Mathias Meyer e7d4b284cd Make action links actual icons.
This change pushes the cog menu to the top, where it belongs, as it
now only includes repository-relevant actions. The icons now reflect
things relating to the build/job itself, and have replace the cog
meny.
2013-09-09 16:40:23 +02:00

45 lines
1.4 KiB
Handlebars

<div id="tools">
<a href="#" {{action "menu" target="view"}} class="menu-popup-button"></a>
<ul class="menu">
{{#if view.displayRegenerateKey}}
<li>
<a href="#" name="regenerate-key"
{{action "regenerateKeyPopup" target="view"}}
{{bindAttr class=":open-popup view.canRegenerateKey::disabled"}}>
Regenerate Key
</a>
</li>
{{/if}}
</ul>
</div>
<div id="regenerate-key" class="popup">
<a href="#" class="close" {{action "popupClose" target="view"}}></a>
<p>
Do you really want to regenerate ssl keys for this repository? Please note that
any data, which is encrypted, such as notification services credentials or secure
environment variables will not be accessible during the builds until you re-encrypt
it with the new key.
</p>
<p>
<a class="sync_now button" {{action "regenerateKey" target="view"}}>Yes, do it!</a>
<span class="or">or</span>
<a href="#" class="cancel" {{action "popupClose" target="view"}}>Cancel</a>
</p>
</div>
<div id="regeneration-success" class="popup">
<a href="#" class="close" {{action "popupClose" target="view"}}></a>
<p>
Key for this repository has been regenerated. If you used previous key
for encryption, you will need encrypt your data again with the new key.
</p>
<p>
You can read more about encryption keys <a href="http://about.travis-ci.org/docs/user/encryption-keys/">in Travis documentation</a>
</p>
</div>