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
f689c0b1
Commit
f689c0b1
authored
Oct 25, 2019
by
Marcel Amirault
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Add link to MR review doc
parent
882ed93c
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
1 addition
and
1 deletion
+1
-1
doc/user/project/merge_requests/index.md
doc/user/project/merge_requests/index.md
+1
-1
No files found.
doc/user/project/merge_requests/index.md
View file @
f689c0b1
...
...
@@ -32,7 +32,7 @@ With GitLab merge requests, you can:
While directly making changes to files in a branch of a repository is possible, it is not
the common workflow. In most cases, a user will
[
create a merge request
](
creating_merge_requests.md
)
,
which is then
reviewed
, updated, approved and merged into the target branch. This is
which is then
[
reviewed
](
reviewing_and_managing_merge_requests.md
)
, updated, approved and merged into the target branch. This is
especially true for merging changes from a feature branch into the master branch.
[
Creating merge requests
](
creating_merge_requests.md
)
, as well as
[
reviewing and managing them
](
#reviewing-and-managing-merge-requests
)
,
...
...
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