Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[FR] Extra push options #319

Closed
lrkwz opened this issue Nov 9, 2021 · 1 comment
Closed

[FR] Extra push options #319

lrkwz opened this issue Nov 9, 2021 · 1 comment

Comments

@lrkwz
Copy link

lrkwz commented Nov 9, 2021

feature request: It would be useful the ability to send extra push options at the start of tasks.
As an example gitlab supports:

git push -o merge_request.create

though

https://git-scm.com/docs/git-push

-o
--push-option=

Transmit the given string to the server, which passes them to the pre-receive as well as the post-receive hook. The given string must not contain a NUL or LF character. When multiple --push-option= are given, they are all sent to the other side in the order listed on the command line. When no --push-option= is given from the command line, the values of configuration variable push.pushOption are used instead.

(see also https://docs.gitlab.com/ee/user/project/push_options.html).

it would be useful have the chance to configure mvn gitflow:feature-start so that it automatically pushes the new branch as soon as it is locally created -DpushRemote=true decorating the push with extra options.

I imagine something like:

<plugin>
    <groupId>com.amashchenko.maven.plugin</groupId>
    <artifactId>gitflow-maven-plugin</artifactId>
    <version>1.16.0</version>
    <configuration>
        <pushRemote>true</pushRemote>
        <pushOptions>
             <merge_request.create />
             <merge_request.target>main</merge_request.target>
        </pushOptions>
    </configuration>
</plugin>
@lrkwz lrkwz changed the title [feature request] Extra push options [FR] Extra push options Nov 9, 2021
@lrkwz
Copy link
Author

lrkwz commented Nov 25, 2021

The only workaround so far is

git config --add push.pushOption merge_request.create

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant