Attribution

Why

Teams don't use mob at all or only for some commands because co-authors aren't properly attributed, and this is very important to those teams.

Scope

mob done --squash

Usually, mob next creates WIP commits and mob done --squash puts all changes in the staging area and the user creates a single commit of all changes at the end.

Approaches:

• Gather all git authors who made a WIP commit and help the user to include those users in some form in the new commit the user will create manually. What about authors that haven't made an actual commit but are still part of the mob?
• Push everything to the user. The user must include their co-authors manually in the commit the user manually creates.

mob done --no-squash without mob next

Every user won't use mob next but instead create all commits in the WIP branch themselves. In the end, mob done --no-squash merges all those commits back in main.

• Do all manual commits require co-authors here as well?

mob done --no-squash with mob next

This combination probably doesn't make a lot of sense. Because who wants a git history with strange WIP commit messages anyway.

mob done --no-squash with mob next --message

This combination might make sense. Not sure yet.