gitlab-org--gitlab-foss/app/views/projects/deploy_keys/_index.html.haml

- expanded = expanded_by_default?
%section.qa-deploy-keys-settings.settings.no-animate#js-deploy-keys-settings{ class: ('expanded' if expanded), data: { qa_selector: 'deploy_keys_settings' } }
  .settings-header
    %h4
      Deploy Keys
    %button.btn.js-settings-toggle{ type: 'button' }
      = expanded ? 'Collapse' : 'Expand'
    %p
      Deploy keys allow read-only or read-write (if enabled) access to your repository. Deploy keys can be used for CI, staging or production servers. You can create a deploy key or add an existing one.
  .settings-content
    %h5.prepend-top-0
      Create a new deploy key for this project
    = render @deploy_keys.form_partial_path
    %hr
    #js-deploy-keys{ data: { endpoint: project_deploy_keys_path(@project), project_id: @project.id } }
Prefer usage of helper `expanded_by_default?` Stop using `Rails.env.test?` in views. 2019-04-29 11:01:28 -04:00			`- expanded = expanded_by_default?`
Add latest changes from gitlab-org/gitlab@master 2020-03-18 23:09:48 -04:00			`%section.qa-deploy-keys-settings.settings.no-animate#js-deploy-keys-settings{ class: ('expanded' if expanded), data: { qa_selector: 'deploy_keys_settings' } }`
Resolve "Simplified Repository Settings page" 2017-06-07 04:11:44 -04:00			`.settings-header`
			`%h4`
Created the gear settings entry and created a way to initialize both sections with one controller Changed views to partials, created the repository view, created a repository_helper to further aid the creation of variables across different controllers 2017-01-23 19:28:40 -05:00			`Deploy Keys`
Port changes from EE. Remove unused class 2019-01-29 12:50:30 -05:00			`%button.btn.js-settings-toggle{ type: 'button' }`
Resolve "Rename settings panel "close" action to "collapse" to avoid confusion" 2017-06-22 10:32:04 -04:00			`= expanded ? 'Collapse' : 'Expand'`
Project deploy keys updated UI Closes #13992 2016-04-25 11:26:41 -04:00			`%p`
Fix inconsistent deploy key documentation in UI Deploy keys were added with write access to https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/7383 - We still state " Deploy keys allow read-only access to your repository." in the UI. This updates the deploy key UI information to reflect the docs https://docs.gitlab.com/ce/ssh/README.html#deploy-keys 2017-03-08 13:14:02 -05:00			`Deploy keys allow read-only or read-write (if enabled) access to your repository. Deploy keys can be used for CI, staging or production servers. You can create a deploy key or add an existing one.`
update settings panels to place "expanded" class on the correct element 2017-10-14 02:10:37 -04:00			`.settings-content`
Project deploy keys updated UI Closes #13992 2016-04-25 11:26:41 -04:00			`%h5.prepend-top-0`
			`Create a new deploy key for this project`
Introduced the deploy keys presenter 2017-01-31 09:12:02 -05:00			`= render @deploy_keys.form_partial_path`
Project deploy keys updated UI Closes #13992 2016-04-25 11:26:41 -04:00			`%hr`
Make deploy keys table more clearly structured 2018-05-07 14:21:34 -04:00			`#js-deploy-keys{ data: { endpoint: project_deploy_keys_path(@project), project_id: @project.id } }`