Skip to content

Security / Display Issue with Commits - who commited? #4422

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

Closed
2 of 7 tasks
cht47 opened this issue Jul 11, 2018 · 3 comments
Closed
2 of 7 tasks

Security / Display Issue with Commits - who commited? #4422

cht47 opened this issue Jul 11, 2018 · 3 comments
Labels
issue/confirmed Issue has been reviewed and confirmed to be present or accepted to be implemented type/feature Completely new functionality. Can only be merged if feature freeze is not active.

Comments

@cht47
Copy link

cht47 commented Jul 11, 2018

  • Gitea version (or commit ref): f096e69 / 1.5
  • Git version: 2.16.4
  • Operating system: CentOS 7.5
  • Database (use [x]):
    • PostgreSQL
    • MySQL
    • MSSQL
    • SQLite
  • Can you reproduce the bug at https://try.gitea.io:
    • Yes (provide example URL)
    • No
    • Not relevant
  • Log gist:

Description

I've added some accounts for students which where working on a research project. It seems like they created multiple SSH Keys and added it to their account to get access to the repository but they didn't set their name/mail address correctly on some computers. Now in the commit history I don't see who did the commit as the name is not clickable and not linked to the gitea account who has access to the private repo.

A solution would be to link every user to the gitea user who has that public SSH key associated with his account.

I'm new to git so sorry if there is an easy git command to get out who commited, but I expect to see this information in gitea :)

Screenshots

gitea_issue

@lafriks
Copy link
Member

lafriks commented Jul 11, 2018

Currently gitea does not support limiting of pushing only own commits. So whatever is written in commit is what will be later used to match users

@lafriks lafriks added the type/feature Completely new functionality. Can only be merged if feature freeze is not active. label Jul 11, 2018
@lafriks
Copy link
Member

lafriks commented Jul 11, 2018

I think there was issue for such feature but I can't seem to find it so leaving this one open for now

@stale
Copy link

stale bot commented Jan 19, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

@stale stale bot added the issue/stale label Jan 19, 2019
@lunny lunny added the issue/confirmed Issue has been reviewed and confirmed to be present or accepted to be implemented label Jan 21, 2019
@stale stale bot removed the issue/stale label Jan 21, 2019
@go-gitea go-gitea locked and limited conversation to collaborators May 3, 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/feature Completely new functionality. Can only be merged if feature freeze is not active.
Projects
None yet
Development

No branches or pull requests

4 participants