Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add co-authors of a pull request when squash-merging #9281

Closed
kolaente opened this issue Dec 7, 2019 · 12 comments
Closed

Add co-authors of a pull request when squash-merging #9281

kolaente opened this issue Dec 7, 2019 · 12 comments
Labels
issue/confirmed Issue has been reviewed and confirmed to be present or accepted to be implemented type/enhancement An improvement of existing functionality

Comments

@kolaente
Copy link
Member

kolaente commented Dec 7, 2019

Currently, Gitea does not add any co-authors to the commit message if there was more than one author in a pull request and the pull request is squash-merged.

I would propose to append a message like the following to the commit message text box when merging:

Co-authored-by: User <[email protected]>

This makes it easier to see with only a git blame later who participated code in that pull request.

@shilch
Copy link
Contributor

shilch commented Dec 7, 2019

It's a common standard for commit message trailers. Here's a list of trailers as a reference.

@shilch
Copy link
Contributor

shilch commented Dec 7, 2019

And this is GitHub doing it.

@guillep2k
Copy link
Member

Interesting. We could add Acked-by: for approvers.

@zeripath
Copy link
Contributor

zeripath commented Dec 7, 2019

Agreed! I wanted to add this to the signing code but realised that it was out of scope.

It does need us to consider if we're squashing if we're going to add the co authors of co authored commits we're squashing too. This means we will likely need to semi parse the commit message...

@guillep2k
Copy link
Member

It does need us to consider if we're squashing if we're going to add the co authors of co authored commits we're squashing too. This means we will likely need to semi parse the commit message...

Interesting. Maybe a two-step feature?

@lunny lunny added the type/enhancement An improvement of existing functionality label Dec 8, 2019
@zeripath
Copy link
Contributor

This is partially fixed by #9393 - A more complete implementation would do the following:

  • Parse the commit messages and find their Co-Authored-By trailers to add those
  • Would skip merges with the base branch and commits that are already in base branch

I if we get both of those would mean that we might have better functionality than GH

@stale
Copy link

stale bot commented Mar 11, 2020

This issue has been automatically marked as stale because it has not had recent activity. I am here to help clear issues left open even if solved or waiting for more insight. This issue will be closed if no further activity occurs during the next 2 weeks. If the issue is still valid just add a comment to keep it alive. Thank you for your contributions.

@stale stale bot added the issue/stale label Mar 11, 2020
@stale
Copy link

stale bot commented Mar 26, 2020

This issue has been automatically closed because of inactivity. You can re-open it if needed.

@stale stale bot closed this as completed Mar 26, 2020
@zeripath zeripath reopened this Mar 27, 2020
@stale stale bot removed the issue/stale label Mar 27, 2020
@zeripath zeripath added the issue/confirmed Issue has been reviewed and confirmed to be present or accepted to be implemented label Mar 27, 2020
@MarcelCoding
Copy link

Is it intended that this is always added, even If the email is the same as the actual committer email?

marcel@marcel:~/stack$ git log
commit 9a0fb7f3f710673ae391bf3d881e53fdfec06577 (HEAD -> main, origin/main, origin/HEAD)
Author: Renovate Bot <[email protected]>
Date:   Tue Aug 9 00:55:37 2022 +0200

    Configure Renovate (#3)

    Reviewed-on: https://git.m4rc3l.de/marcel/stack/pulls/3
    Co-authored-by: Renovate Bot <[email protected]>
    Co-committed-by: Renovate Bot <[email protected]>

@Basitx72
Copy link

Co-authored-by: Maverick920 [email protected]

@Preetiraj3697
Copy link

Co-authored-by: Preetiraj3697 [email protected]

@ares-dev05
Copy link

Co-authored-by: ares9515 [email protected]

@go-gitea go-gitea locked as resolved and limited conversation to collaborators Feb 17, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
issue/confirmed Issue has been reviewed and confirmed to be present or accepted to be implemented type/enhancement An improvement of existing functionality
Projects
None yet
Development

No branches or pull requests

10 participants