Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
G
gitlab-ce
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
1
Merge Requests
1
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
nexedi
gitlab-ce
Commits
95d1fc03
Commit
95d1fc03
authored
Dec 04, 2020
by
John Feeney
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Fixed a typo (missing word) in documentation on Deploy Keys
parent
9b516b9c
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
1 addition
and
1 deletion
+1
-1
doc/user/project/deploy_keys/index.md
doc/user/project/deploy_keys/index.md
+1
-1
No files found.
doc/user/project/deploy_keys/index.md
View file @
95d1fc03
...
...
@@ -27,7 +27,7 @@ repository in automation, it's a simple solution.
A drawback is that your repository could become vulnerable if a remote machine is compromised
by a hacker. You should limit access to the remote machine before a deploy key is
enabled on your repository. A good rule to follow is to access only to trusted users,
enabled on your repository. A good rule to follow is to
provide
access only to trusted users,
and make sure that the allowed users have
[
maintainer permissions or higher
](
../../permissions.md
)
in the GitLab project.
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment