DOC Note on commit co-authorship when merging PRs #16550
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
A short note to raise awareness of @scikit-learn/core-devs that multiple co-authors can be attributed in git when merging PRs. The
Co-authored-by
tag pre-filled by Github needs to be kept in the detailed description for it to happen.When to give co-authorship is left it maintainers appreciation, but I think there are at least the following cases where it could make sense to reflect co-authorship in git blame,
Note that Github already does this by default, unless ones removes the detailed commit description when merging PRs.