|Re: [hatari-devel] MODE SENSE patch|
[ Thread Index |
| More lists.tuxfamily.org/hatari-devel Archives
- To: hatari-devel@xxxxxxxxxxxxxxxxxxx
- Subject: Re: [hatari-devel] MODE SENSE patch
- From: Miro Kropáček <miro.kropacek@xxxxxxxxx>
- Date: Mon, 21 Mar 2022 08:53:08 +0100
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=pjPsJHzhmYF384WfwKiLC8MkJlT5onpZ0GZatDPxEwM=; b=WxcIUIK+C5nBVUPLMRKAQz2eUXjiHVSDYyK1d1fUYNEwmrEGVgPV1B/Q/d7O0MMYac CWfvJM3CcFmqptoW4HEz48xHJlJZWXbSBEHE+x7qzwxOtbAX12TWepjbSELAIe2cwy8E 11ZxWfxpckF2dkxkO3lV/VGxjWOklaQQNhs+epdPFw0fiN4P1VhdaooCp9Y9x1cfsrHI d3RwA3+/zmu3YOq/551kSNM8IaVxcD/UtEag+kTYjFKcQpH1mnZUYWA+ycX/8iQR7N4J JQeErBsxXBlbrxVFkSjd2Cjxp8KqGb25Imqf0ORygauqjmR1m0qQKJGslKNktrlVpX06 vc4A==
Miro, do you know whether one can configure GitHub to not let others merge
your PRs? Usually only the owner of a PR knows how to meaningfully edit the
squash merge commit message, but if somebody else approves the PR and then
merges one usually ends up with the default message.
Nothing that I am aware of. Gitlab allows a "work in progress" label on your PR and a rule that PR can't be merged unless a certain amount of people approves it but that's it.
I guess the best approach in Github is to either directly specify what you want to happen with your PR (squash/rebase/merge) with what comment or to agree with the maintainers in what way the commits will be merged for everyone (and prepare the commit(s) in the way that it works by default).