<!--IssueSummary start--> <details> <summary> Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards. </summary> - [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=526258) </details> <!--IssueSummary end--> ### Release notes Better recognise contributors' contributions by capturing co-authorship even if the commit message is changed when applying suggestions. ### Problem to solve If a number of contributors leave suggestions on a merge request and they are added to batch. I have two options: - Add a really non-descriptive commit message "Applying 3 suggestions to 2 files" with co-authorship - Add my own commit message, but the co-authorship disappears I can manually add co-authorship back, but this takes time and involves double checking who submitted suggestions, and then getting their email and writing it in the correct format. ### Intended users _Sorry, I didn't read all of the personas!_ *Main user:* Users accepting suggestions with clear commit messages. *Main beneficiary*: ### User experience goal This improves user experience for two main groups: - **Users accepting suggestions** - Saving them time not manually re-adding attribution of co-authorship, - **Contributors making suggestions** - Attribution of co-authorship can be meaningful especially to new contributors. This tends to get deleted if people are not aware that it isn't automatically appended. ### Proposal When you start typing a commit message now it deletes the entire auto-generated message. It would be good to delete the `applying N suggestions to M files` but keep the co-authorship lines. ### Further details None ### Permissions and Security Shouldn't have any security implications ### Documentation I believe this would be expected behaviour, so I don't believe it would need extra documentation? ### Availability & Testing <!-- This section needs to be retained and filled in during the workflow planning breakdown phase of this feature proposal, if not earlier. What risks does this change pose to our availability? How might it affect the quality of the product? What additional test coverage or changes to tests will be needed? Will it require cross-browser testing? Please list the test areas (unit, integration and end-to-end) that needs to be added or updated to ensure that this feature will work as intended. Please use the list below as guidance. * Unit test changes * Integration test changes * End-to-end test change See the Quality Engineering quad planning and test planning processes and reach out to your counterpart Software Engineer in Test for assistance. Quad Planning: https://handbook.gitlab.com/handbook/engineering/infrastructure/test-platform/quad-planning/ Test Planning: https://handbook.gitlab.com/handbook/engineering/infrastructure/test-platform/test-engineering/#test-planning --> ### Available Tier Free please :angel: <!-- This section should be used for setting the appropriate tier that this feature will belong to. Pricing can be found here: https://about.gitlab.com/pricing/ * Free * Premium/Silver * Ultimate/Gold --> ### Feature Usage Metrics If you really wanted to track it, you could see if co-authorship messages increase. ### What does success look like, and how can we measure that? Happy new contributors being accepted. ### What is the type of buyer? <!-- What is the buyer persona for this feature? See https://handbook.gitlab.com/handbook/marketing/brand-and-product-marketing/product-and-solution-marketing/roles-personas/buyer-persona/ In which enterprise tier should this feature go? See https://handbook.gitlab.com/handbook/company/pricing/#three-tiers --> ### Is this a cross-stage feature? <!-- Communicate if this change will affect multiple Stage Groups or product areas. We recommend always start with the assumption that a feature request will have an impact into another Group. Loop in the most relevant PM and Product Designer from that Group to provide strategic support to help align the Group's broader plan and vision, as well as to avoid UX and technical debt. https://about.gitlab.com/handbook/product/#cross-stage-features --> ### What is the competitive advantage or differentiation for this feature? ### Links / references <!-- Label reminders Make sure to add the appropriate labels for the product stage and/or group (e.g ~"devops::plan") if known and add a comment tagging the appropriate Product Manager. Use the following resources to find the appropriate labels: - Use only one tier label choosing the lowest tier this is intended for - https://gitlab.com/gitlab-org/gitlab/-/labels - https://about.gitlab.com/handbook/product/categories/features/ Examples: /label ~group:: ~section:: ~Category: /label ~"GitLab Free" ~"GitLab Premium" ~"GitLab Ultimate" -->