Updated readme with instructions to fetch MRs from origin. #370
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| * Add a second repository with: | ||
| * *URL*: Your *Repository URL* as in the previous step (e.g.: ``[email protected]:group/repo_name.git``) | ||
| 4. In *Branch Specifier* enter: | ||
| * ``merge-requests/${gitlabMergeRequestIid}`` |
There was a problem hiding this comment.
Is this a typo?
${gitlabMergeRequestIid}
There was a problem hiding this comment.
Not a typo. GitLab uses both id and iid. id refers to the internal ID in their DB, and iid to the user facing number (in tickets or Merge Requests). In this case, we need the user facing one.
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In my pursue of wrapping up #285, I realised that it's possible to achieve the same effect (i.e. fetching Merge Requests from the
upstreamrepository) just by means of adjusting the configuration a little bit.This Readme changes reflect that, and doesn't carry the current limitations in #285 (re-build open MRs, etc.)