Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>

Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>

Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>

From both experimenting with the API and reading the source code, this appears to not be used at all.

My guess is this was copypasta from somewhere else.

Remove emphasis from system notes to avoid Markdown conflicts in names.

Signed-off-by: Jeroen van Baarsen <jeroenvanbaarsen@gmail.com>

The description can be provided when creating or updating a merge
request.

Signed-off-by: Loic Dachary <loic@dachary.org>

# The first commit's message is:

Patched `MergeRequest` to return more data.

Patched `MergeRequest` to return the `description` & `milestone`
Conflicts:
	lib/api/entities.rb

# This is the 2nd commit message:

Update merge_requests.md

Update documentation for merge request endpoint adding support for description.

Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>

Added description about optional field target_project_id for merge requests.

Add an optional parameter to list merge requests to restrict the
returned merge requests to those that are "opened", "merged" or
"closed". By default all merge requests are returned. Note that
"all" can be given to explicitly request all merge requests.

Fixes: #5505

Add method to get the comments for a merge request and
document that you can change the status of a merge request.

Signed-off-by: Islam Amer <islam.amer@jollamobile.com>

All the info to return codes from the API functions are available in the `README.md` file as suggested.

The API documentation of merge requests contains info to status codes for all functions.
Required arguments are now checked in the merge requests API functions and a `400 Bad Request` error is
returned if they are not given.