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
2516fc94
Commit
2516fc94
authored
Mar 15, 2019
by
GitLab Bot
Browse files
Options
Browse Files
Download
Plain Diff
Automatic merge of gitlab-org/gitlab-ce master
parents
5e47201c
480303b5
Changes
2
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
with
2 additions
and
2 deletions
+2
-2
doc/ci/review_apps/index.md
doc/ci/review_apps/index.md
+1
-1
doc/user/project/badges.md
doc/user/project/badges.md
+1
-1
No files found.
doc/ci/review_apps/index.md
View file @
2516fc94
...
...
@@ -12,7 +12,7 @@ Review Apps are a collaboration tool that takes the hard work out of providing a
Review Apps:
-
Provide an automatic live preview of changes made in a feature branch by spinning up a dynamic environment for your merge requests.
-
Allow designers and product manages to see your changes without needing to check out your branch and run your changes in a sandbox environment.
-
Allow designers and product manage
r
s to see your changes without needing to check out your branch and run your changes in a sandbox environment.
-
Are fully integrated with the
[
GitLab DevOps LifeCycle
](
../../README.md#the-entire-devops-lifecycle
)
.
-
Allow you to deploy your changes wherever you want.
...
...
doc/user/project/badges.md
View file @
2516fc94
...
...
@@ -63,7 +63,7 @@ are available:
-
`%{commit_sha}`
: ID of the most recent commit to the default branch of a
project's repository
NOTE:
**N
OTE
**
NOTE:
**N
ote:
**
Placeholders allow badges to expose otherwise-private information, such as the
default branch or commit SHA when the project is configured to have a private
repository. This is by design, as badges are intended to be used publicly. Avoid
...
...
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