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
11c12117
Commit
11c12117
authored
Dec 07, 2020
by
GitLab Bot
Browse files
Options
Browse Files
Download
Plain Diff
Automatic merge of gitlab-org/gitlab master
parents
3e9185ad
c00bc691
Changes
3
Show whitespace changes
Inline
Side-by-side
Showing
3 changed files
with
11 additions
and
20 deletions
+11
-20
doc/administration/packages/container_registry.md
doc/administration/packages/container_registry.md
+6
-0
doc/development/documentation/styleguide/index.md
doc/development/documentation/styleguide/index.md
+3
-20
doc/user/project/import/github.md
doc/user/project/import/github.md
+2
-0
No files found.
doc/administration/packages/container_registry.md
View file @
11c12117
...
...
@@ -1137,6 +1137,12 @@ and a simple solution would be to enable relative URLs in the Registry.
### Enable the Registry debug server
You can use the Container Registry debug server to diagnose problems. The debug endpoint can monitor metrics and health, as well as do profiling.
CAUTION:
**Warning:**
Sensitive information may be available from the debug endpoint.
Access to the debug endpoint must be locked down in a production environment.
The optional debug server can be enabled by setting the registry debug address
in your
`gitlab.rb`
configuration.
...
...
doc/development/documentation/styleguide/index.md
View file @
11c12117
...
...
@@ -1799,25 +1799,8 @@ in the GitLab product documentation.
### Avoid line breaks in names
Product names, feature names, and non-GitLab products that contain spaces
shouldn't be split across lines.
For example: GitLab Community Edition or Amazon Web Services.
Splitting product or feature names across lines makes searching for these items
more difficult, and can cause problems if names change.
For example, the following Markdown content is _not_ formatted correctly:
```
markdown
When entering a product or feature name that includes a space (such as GitLab
Community Edition), don't split the product or feature name across lines.
```
Instead, it should appear similar to the following:
```
markdown
When entering a product or feature name that includes a space (such as
GitLab Community Edition), don't split the product or feature name across lines.
```
If a feature or product name contains spaces, don't split the name with a line break.
When names change, it is more complicated to search or grep text that has line breaks.
### Product tier badges
...
...
doc/user/project/import/github.md
View file @
11c12117
...
...
@@ -23,6 +23,8 @@ The following aspects of a project are imported:
-
Labels (GitLab.com & 8.7+)
-
Release note descriptions (GitLab.com & 8.12+)
-
Pull request review comments (GitLab.com & 10.2+)
-
Pull request reviews (GitLab.com & 13.7+)
-
Pull request "merged by" information (GitLab.com & 13.7+)
-
Regular issue and pull request comments
-
[
Git Large File Storage (LFS) Objects
](
../../../topics/git/lfs/index.md
)
...
...
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