The cli works as expected:
Invoking pr create --maintainer-edit=false
Resulted in:

(Which i'm now going to enable manually through the WebUI)

I agree, i dont like the name of the flag either.
Alternatively we could switch from a positive flag to --deny-maintainer-edit (also not a fan of the name), which would then allow to leave out =false as well.

I guess i'm too familiar with unix like systems, as that is an intuitive concept to me! Where do you think should the documentation reside? I guess including both the example from above within the examples and a short notice within the long text would be adaquate then right?

How about:

&cobra.Command{
                // [...]
		Long: heredoc.Doc(`
			Create a pull request on GitHub.

			When the current branch isn't fully pushed to a git remote, a prompt will ask where
			to push the branch and offer an option to fork the base repository. Use '--head' to
			explicitly skip any forking or pushing behavior.

			A prompt will also ask for the title and the body of the pull request. Use '--title'
			and '--body' to skip this, or use '--fill' to autofill these values from git commits.

                        By default users with write access to the base respository can add new commits to your branch.
                        If undesired, you may disable access of maintainers by using '--maintainer-edit=false' 
                        You can always change this setting later.
		`),
		Example: heredoc.Doc(`
			$ gh pr create --title "The bug is fixed" --body "Everything works again"
			$ gh pr create --reviewer monalisa,hubot
			$ gh pr create --project "Roadmap"
			$ gh pr create --base develop --head monalisa:feature
			$ gh pr create --maintainer-edit=false
		`),
                 // [...]
}

While i agree we should definitely throw an error if the web based access does not allow to pass the flag. However i would suggest, as this is a github product, and the Web UI already supports this field, to adapt and change this behavior, if possible.
In meantime i can add an error accordingly 👍 .

I'll add my changes this evening.

Hey there, thank you for picking the issue up so quickly! I hope you are all well!

From my "user perspective" a name like --no-maintainer-access / --no-external-access seems best, because the flag switches one thing and there is no need for key-value semantics. This is also exactly how I understand the similar --draft flag. I want to amend here that not only maintainers, but everyone that has write access to a repository gets access to a PR branch if the setting is not disabled. Although the checkbox on github.com reads "maintainer", this flag here should maybe reflect this more closely, hence the

/ --no-external-access

Anyway, thank you all for your work on this project, I use it all the time!

@mislav As the design might still take some time, mind adding a hacktoberfest-accepted label? If you need any changes, feel free to suggest them 😄 .

#1308

going with --no-maintainer-edit, i'll see it through