<!--- Please read this! Before opening a new issue, make sure to search for keywords in the issues filtered by the "bug" label: - https://gitlab.com/gitlab-org/cli/-/issues/?label_name%5B%5D=type%3A%3Abug and verify the issue you're about to submit isn't a duplicate. ---> ### Checklist <!-- Please test the latest versions, that will remove the possibility that you see a bug that is fixed in a newer version. --> - [ ] I'm using the latest version of the extension (Run `glab --version`) - [ ] Operating System and version: macos 13.2 ### Summary When using glab mr create, it pushes the changes but i haven't told it to. ### Steps to reproduce Original reproduction steps: 1. ~`glab mr create -f -y` on pushed branch~ Refined reproduction steps: 1. Execute `glab mr create -f --push=false` 2. Create the MR 3. Observe that the latest unpushed commits are pushed to the remote branch. ### What is the current _bug_ behavior? It makes a push triggering my git hooks ### What is the expected _correct_ behavior? Do not push since i haven't specified the --push ### Relevant logs and/or screenshots   ### Possible fixes Remove the [override](https://gitlab.com/gitlab-org/cli/-/blob/b6b6658a4a2341650942d4413e52d7aeeaffc7df/commands/mr/create/mr_create.go#L361-372) done when the `--fill` flag is set to `true`.