From: #38 (comment)

We were discussing the process of merging standard PRs for two reasons:

1. We would like to keep the original contributor commit signature.
2. In the future we would like to have at least two branches (GitFlow: main and develop) and use only bot signatures when merging into main or other automatically managed branches.

Thre draft process could be:

• Contributor forks the repo.
• Contributor creates a new branch issue-xxxx-description in the fork.
• Contributor creates commits and push to the branch in the fork.
• Contributor creates a PR into main in the upstream repo.
• If it's all ok we merge with:

git checkout main
git pull
git checkout -b contributor-fork-issue-xxxx-description main
git pull https://github.com/contributor/git-queue.git issue-xxxx-description
git checkout main
git merge --no--ff contributor-fork-issue-xxxx-description
git push origin main

If there are new commis in the main branch:

Contributor has to rebase their branch (signing new commits with their GPGP keys).
Go back to the previous state and merge.
The commit is signed with the Nautilus bot GPG key and shown as partially verified.

With git merge --ff-only we would not lose the contributor's commit signature if we did not use the bot signature. Right now we get partially verified commits because the commit changes because we sign it again with a different GPG key (and we change the committer).

UPDATE:

With git merge we do not lose the contributor's commit signature.