Wrong author when creating a project in an organization #5076

New Issue

GiteaMirror · 2025-11-02T06:13:34-06:00

GiteaMirror commented

2025-11-02 06:13:34 -06:00

Originally created by @mcnesium on GitHub (Mar 18, 2020).

Gitea version (or commit ref): 1.12.0+dev-15-g28b934b3a (Docker image: gitea/gitea)
Can you reproduce the bug at https://try.gitea.io:
- Yes https://try.gitea.io/Test_Inc./testproject

Description

When creating a new project in an organization and checking "Initialize repository", the author of the first commit is not the user who did it, but instead the name of the organization. This is sort of misleading. Imho the author of a commit should always be a person, and thus it should be the user who created the project in that organization.

Originally created by @mcnesium on GitHub (Mar 18, 2020). - Gitea version (or commit ref): 1.12.0+dev-15-g28b934b3a (Docker image: gitea/gitea) - Can you reproduce the bug at https://try.gitea.io: - [x] Yes https://try.gitea.io/Test_Inc./testproject ## Description When creating a new project in an organization and checking "Initialize repository", the author of the first commit is not the user who did it, but instead the name of the organization. This is sort of misleading. Imho the author of a commit should always be a person, and thus it should be the user who created the project in that organization.

GiteaMirror added the type/enhancement label 2025-11-02 06:13:34 -06:00

GiteaMirror closed this issue

2025-11-02 06:13:34 -06:00

GiteaMirror commented

2025-11-02 06:13:35 -06:00

@stale[bot] commented on GitHub (May 20, 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[bot] commented on GitHub (May 20, 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.

GiteaMirror commented

2025-11-02 06:13:35 -06:00

@mcnesium commented on GitHub (May 22, 2020):

unstale

@mcnesium commented on GitHub (May 22, 2020): unstale

GiteaMirror referenced this issue

2025-11-02 14:33:50 -06:00

[PR #5076] [MERGED] fix release creation via API #17625

Sign in to join this conversation.