<!-- This issue template can be used as a great starting point for feature requests. The section "Release notes" can be used as a summary of the feature and is also required if you want to have your release post blog MR auto generated using the release post item generator: https://about.gitlab.com/handbook/marketing/blog/release-posts/#release-post-item-generator. The remaining sections are the backbone for every feature in GitLab. The goal of this template is brevity for quick/smaller iterations. For a more thorough list of considerations for larger features or feature sets, you can leverage the detailed [feature proposal](https://gitlab.com/gitlab-org/gitlab/-/blob/master/.gitlab/issue_templates/Feature%20proposal%20-%20detailed.md). --> ### Release notes <!-- What is the problem and solution you're proposing? This content sets the overall vision for the feature and serves as the release notes that will populate in various places, including the [release post blog](https://about.gitlab.com/releases/categories/releases/) and [Gitlab project releases](https://gitlab.com/gitlab-org/gitlab/-/releases). " --> ### Problem to solve When using the `merge_request.target=<target>` push option without also giving `merge_request.creat`, Gitlab replies with the following error: ``` remote: ======================================================================== remote: remote: WARNINGS: Error encountered with push options remote: 'merge_request.target=<target>': A merge_request.create push option remote: is required to create a merge request for branch remote: <source> remote: remote: ======================================================================== remote: remote: To create a merge request for <source>, visit: remote: https://gitlab.com/<project>/-/merge_requests/new?merge_request%5Bsource_branch%5D=<source> remote: ``` This is very clear, but it could also provide a link with the target branch already set. And simplify creating the merge request via the URL. ### Proposal Using `merge_request.*` push options should work without `merge_request.create` and update the URL. ```bash $ git push -o merge_request.target=<target> origin <source> remote: remote: To create a merge request for <source> visit: remote: https://gitlab.com/<project>/-/merge_requests/new?merge_request%5Bsource_branch%5D=<source>&merge_request%5Btarget_branch%5B=<target> remote: ``` ### Feature Usage Metrics <!-- How are you going to track usage of this feature? Think about user behavior and their interaction with the product. What indicates someone is getting value from it? Explore (../../doc/development/internal_analytics/internal_event_instrumentation/quick_start.md) for a guide. --> ### Does this feature require an audit event? <!--- Checkout these docs to know more https://docs.gitlab.com/ee/development/audit_event_guide/#what-are-audit-events https://docs.gitlab.com/ee/administration/audit_events.html ---> <!-- Label reminders Use the following resources to find the appropriate labels: - Use only one tier label choosing the lowest tier this is intended for - https://gitlab.com/gitlab-org/gitlab/-/labels - https://about.gitlab.com/handbook/product/categories/features/ -->