[Feature Request] can organization have a README.md instead of plain text description? #7806

New Issue

GiteaMirror · 2025-11-02T07:37:18-06:00

GiteaMirror commented

2025-11-02 07:37:18 -06:00

Originally created by @wameup on GitHub (Sep 6, 2021).

This is a feature suggestion. Sometimes organizations need more expressive description instead of plain text.

For example,

There could be hierarchical organizations such as 'company', 'company-admin', 'company-admin-personnel', or 'top-project', 'sub-project1', 'sub-project2'. ==> It's nice to have some hyperlinks in each organization's description, such that I can navigate between the hierarchy.
I want to copy a list of all repository names in an organization, so that I can clone them all in one command.
It's nice for organizations to have a 'homepage', just like README.md file in repositories.

Anyway, if organizations have README.md files just like repositories do, it could be much more expressive and useful.

Originally created by @wameup on GitHub (Sep 6, 2021). This is a feature suggestion. Sometimes organizations need more expressive description instead of plain text. For example, - There could be hierarchical organizations such as 'company', 'company-admin', 'company-admin-personnel', or 'top-project', 'sub-project1', 'sub-project2'. ==> It's nice to have some hyperlinks in each organization's description, such that I can navigate between the hierarchy. - I want to copy a list of all repository names in an organization, so that I can clone them all in one command. - It's nice for organizations to have a 'homepage', just like README.md file in repositories. Anyway, if organizations have README.md files just like repositories do, it could be much more expressive and useful.

GiteaMirror added the type/proposal label 2025-11-02 07:37:18 -06:00

GiteaMirror closed this issue

2025-11-02 07:37:19 -06:00

GiteaMirror commented

2025-11-02 07:37:20 -06:00

@lunny commented on GitHub (May 9, 2023):

Since #23260 merge, I think this is not difficult.

@lunny commented on GitHub (May 9, 2023): Since #23260 merge, I think this is not difficult.

GiteaMirror commented

2025-11-02 07:37:20 -06:00

@wameup commented on GitHub (May 9, 2023):

great!

@wameup commented on GitHub (May 9, 2023): great!

GiteaMirror commented

2025-11-02 07:37:20 -06:00

@delvh commented on GitHub (May 9, 2023):

(However, the mentioned PR only implements this for users, not for orgs which this issue seems to be concerned with)

@delvh commented on GitHub (May 9, 2023): (However, the mentioned PR only implements this for users, not for orgs which this issue seems to be concerned with)

GiteaMirror commented

2025-11-02 07:37:20 -06:00

@npease18 commented on GitHub (May 9, 2023):

I did no testing on organizational profiles. I'll start looking into this

@npease18 commented on GitHub (May 9, 2023): I did no testing on organizational profiles. I'll start looking into this

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#7806