.profile Feature Not Working for Organizations #12397

New Issue

GiteaMirror · 2025-11-02T10:08:35-06:00

GiteaMirror commented

2025-11-02 10:08:35 -06:00

Originally created by @miztizm on GitHub (Jan 27, 2024).

Description

The .profile functionality, while operational for individual user profiles, appears to be non-functional for organization accounts. Despite the official documentation stating its applicability for both user and organization profiles, the feature doesn't seem to work as intended for organizations.

Steps to Reproduce:

Create a .profile repository under an organization account.
Add a README.md file to the .profile repository with relevant organization information.
Push the changes and navigate to the organization's main org page.

Expected Behavior:

The content of the README.md file from the .profile repository should be displayed on the organization's main org page, similar to how it works on individual user profiles.

Actual Behavior:

The README.md content from the .profile repository is not displayed on the organization's main org page. The page appears as it would without the .profile repository.

Gitea Version

1.21.4

Can you reproduce the bug on the Gitea demo site?

No

Log Gist

No response

Screenshots

No response

Git Version

2.39.2

Operating System

Debian

How are you running Gitea?

as a service on debian

Database

MySQL/MariaDB

Originally created by @miztizm on GitHub (Jan 27, 2024). ### Description The `.profile` functionality, while operational for individual user profiles, appears to be non-functional for organization accounts. Despite the [official documentation](https://docs.gitea.com/next/usage/profile-readme) stating its applicability for both user and organization profiles, the feature doesn't seem to work as intended for organizations. ### Steps to Reproduce: 1. Create a `.profile` repository under an organization account. 2. Add a README.md file to the `.profile` repository with relevant organization information. 3. Push the changes and navigate to the organization's main org page. ### Expected Behavior: The content of the README.md file from the `.profile` repository should be displayed on the organization's main org page, similar to how it works on individual user profiles. ### Actual Behavior: The README.md content from the `.profile` repository is not displayed on the organization's main org page. The page appears as it would without the `.profile` repository. ### Gitea Version 1.21.4 ### Can you reproduce the bug on the Gitea demo site? No ### Log Gist _No response_ ### Screenshots _No response_ ### Git Version 2.39.2 ### Operating System Debian ### How are you running Gitea? as a service on debian ### Database MySQL/MariaDB

GiteaMirror added the type/bug label 2025-11-02 10:08:35 -06:00

GiteaMirror closed this issue

2025-11-02 10:08:36 -06:00

GiteaMirror commented

2025-11-02 10:08:36 -06:00

@6543 commented on GitHub (Jan 27, 2024):

you run gitea v1.21.4 - you will need v1.22.x witch is not jet released.

as you already linked to the docs for next...

related pull: #27955

@6543 commented on GitHub (Jan 27, 2024): you run gitea v1.21.4 - you will need v1.22.x witch is not jet released. as you already linked to the docs for `next`... related pull: #27955

GiteaMirror commented

2025-11-02 10:08:36 -06:00

@github-actions[bot] commented on GitHub (Feb 29, 2024):

Automatically locked because of our CONTRIBUTING guidelines

@github-actions[bot] commented on GitHub (Feb 29, 2024): Automatically locked because of our [CONTRIBUTING guidelines](https://github.com/go-gitea/gitea/blob/main/CONTRIBUTING.md#issue-locking)

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/gitea#12397