Even on a squashed merge there is traceability back to the PR and therefore ALL the history will be on the mailing list and publically available on GH.
This is why a rebase work flow has to stop after review. (With some exceptions) but we always attribute to the Authors -----Original Message----- From: Gregory Nutt [mailto:[email protected]] Sent: Wednesday, December 25, 2019 6:44 AM To: [email protected] Subject: Re: Software release life cycle choices could have implications on workflow (was RE: Single Committer) > If they are related / dependent on each other, then I think those > kinds of patchsets should be encapsulated in one branch. That would work fine provided that the branch is not squashed to master. That loses authorship of individual contributions.
