github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-03-12 10:39:38 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

Add wiki page at organization level #3395

New Issue
Closed
opened 2025-11-02 05:11:34 -06:00 by GiteaMirror · 22 comments
GiteaMirror commented 2025-11-02 05:11:34 -06:00
Owner
Copy Link

Originally created by @Xumeiquer on GitHub (May 29, 2019).

Some organizations has several projects that belongs to a big project, like those that have backend or server side and frontend or client.

That would be amazing to have a kind of wiki page for the organization so it would be unique entry point where the organization could explain the whole project and any other projects and finally each project will have its own documentation as usual.

Thanks.

Update: since Gitea has "org profile readme" feature (#27955 and #32872), there could be a pretty good workaround for this case:

Org admin could create wiki under their "org profile" or "org private profile", and use org profile readme to describe it and link the wiki to org's home page. It is more flexible than hard-coded wiki link.

Originally created by @Xumeiquer on GitHub (May 29, 2019). Some organizations has several projects that belongs to a big project, like those that have backend or server side and frontend or client. That would be amazing to have a kind of wiki page for the organization so it would be unique entry point where the organization could explain the whole project and any other projects and finally each project will have its own documentation as usual. Thanks. ---- Update: since Gitea has "org profile readme" feature (#27955 and #32872), there could be a pretty good workaround for this case: Org admin could create wiki under their "org profile" or "org private profile", and use org profile readme to describe it and link the wiki to org's home page. It is more flexible than hard-coded wiki link.
GiteaMirror commented 2025-11-02 05:11:35 -06:00
Author
Owner
Copy Link

@Xumeiquer commented on GitHub (Oct 9, 2019):

Are there any news on this? any plan when is it going to be added?

@Xumeiquer commented on GitHub (Oct 9, 2019): Are there any news on this? any plan when is it going to be added?
GiteaMirror commented 2025-11-02 05:11:35 -06:00
Author
Owner
Copy Link

@lunny commented on GitHub (Oct 9, 2019):

Nobody are working on this.

@lunny commented on GitHub (Oct 9, 2019): Nobody are working on this.
GiteaMirror commented 2025-11-02 05:11:35 -06:00
Author
Owner
Copy Link

@Xumeiquer commented on GitHub (Jan 28, 2020):

I would like to help by adding this feature.

My idea is to add one wiki page at the organization level, which acts as a documentation entry point for further documentation on each repo wiki site, for instance.

Key points:

  • The org admin will be able to enable o to disable the wiki page
  • Org admin or any team admin will be able to edit the wiki page

How does it sound?

@Xumeiquer commented on GitHub (Jan 28, 2020): I would like to help by adding this feature. My idea is to add one wiki page at the organization level, which acts as a documentation entry point for further documentation on each repo wiki site, for instance. Key points: * The org admin will be able to enable o to disable the wiki page * Org admin or any team admin will be able to edit the wiki page How does it sound?
GiteaMirror commented 2025-11-02 05:11:36 -06:00
Author
Owner
Copy Link

@guillep2k commented on GitHub (Jan 28, 2020):

@Xumeiquer Thanks for your offer. I think most of the structure required for this functionality is currently supported by Gitea. Almost . IMHO, what needs to be done is:

  • Provide a setting at the org level to set some repository as the wiki home.
  • Set up a link to the wiki in the organization page.
  • Support the wiki being public while other parts of the repository (code, issues, etc.) are not.

The tricky part is the last one, as changing the permissions structure require a lot of planning. #9787 will certainly help with this task when it's finished.

@guillep2k commented on GitHub (Jan 28, 2020): @Xumeiquer Thanks for your offer. I think most of the structure required for this functionality is currently supported by Gitea. _Almost_ . IMHO, what needs to be done is: - Provide a setting at the org level to set some repository as the wiki home. - Set up a link to the wiki in the organization page. - Support the wiki being public while other parts of the repository (code, issues, etc.) are not. The tricky part is the last one, as changing the permissions structure require a lot of planning. #9787 will certainly help with this task when it's finished.
GiteaMirror commented 2025-11-02 05:11:36 -06:00
Author
Owner
Copy Link

@lunny commented on GitHub (Jan 29, 2020):

I think we can create a repository named <org_name>/_default.wiki.git and reverse the name _default.

@lunny commented on GitHub (Jan 29, 2020): I think we can create a repository named `<org_name>/_default.wiki.git` and reverse the name `_default`.
GiteaMirror commented 2025-11-02 05:11:36 -06:00
Author
Owner
Copy Link

@Xumeiquer commented on GitHub (Jan 29, 2020):

@guillep2k I can start working on the first two bullet points and leave the last one until the #9787 will be finished. Thus the wiki repo at org level will be private for now.

@lunny I think it is a good approach.

@Xumeiquer commented on GitHub (Jan 29, 2020): @guillep2k I can start working on the first two bullet points and leave the last one until the #9787 will be finished. Thus the wiki repo at org level will be private for now. @lunny I think it is a good approach.
GiteaMirror commented 2025-11-02 05:11:36 -06:00
Author
Owner
Copy Link

@erikhuck commented on GitHub (Sep 28, 2021):

@Xumeiquer Is there a way to have a wiki for an organization now? I can't find that option for my organization.

@erikhuck commented on GitHub (Sep 28, 2021): @Xumeiquer Is there a way to have a wiki for an organization now? I can't find that option for my organization.
GiteaMirror commented 2025-11-02 05:11:36 -06:00
Author
Owner
Copy Link

@mpiorowski commented on GitHub (Aug 8, 2022):

Any updates on that issue? This would solve so much organization problems for us :)

@mpiorowski commented on GitHub (Aug 8, 2022): Any updates on that issue? This would solve so much organization problems for us :)
GiteaMirror commented 2025-11-02 05:11:37 -06:00
Author
Owner
Copy Link

@lunny commented on GitHub (Aug 8, 2022):

The web URL could be <org_name>/-/wiki and the clone URL could be <org_name>.wiki.git.

@lunny commented on GitHub (Aug 8, 2022): The web URL could be `<org_name>/-/wiki` and the clone URL could be `<org_name>.wiki.git`.
GiteaMirror commented 2025-11-02 05:11:37 -06:00
Author
Owner
Copy Link

@Xumeiquer commented on GitHub (Oct 17, 2022):

I have some spear time and want to catch up on this.

@Xumeiquer commented on GitHub (Oct 17, 2022): I have some spear time and want to catch up on this.
GiteaMirror commented 2025-11-02 05:11:37 -06:00
Author
Owner
Copy Link

@dinbtechit commented on GitHub (Nov 11, 2022):

Any update on this? This is a pretty vital feature.

@dinbtechit commented on GitHub (Nov 11, 2022): Any update on this? This is a pretty vital feature.
GiteaMirror commented 2025-11-02 05:11:37 -06:00
Author
Owner
Copy Link

@Xumeiquer commented on GitHub (Nov 13, 2022):

Playing with the source code I find this functionality to be the same as the Wiki at the repository level. Adding all the needed code for the Org Wiki will duplicate code and functionality.

What will be the best approach?

  1. Reuse the code at the repository level and do any adjustment, if needed.
  2. Or, duplicate the wiki code at the Org level.
  3. Any other approach I am not aware of.
@Xumeiquer commented on GitHub (Nov 13, 2022): Playing with the source code I find this functionality to be the same as the Wiki at the repository level. Adding all the needed code for the Org Wiki will duplicate code and functionality. What will be the best approach? 1. Reuse the code at the repository level and do any adjustment, if needed. 2. Or, duplicate the wiki code at the Org level. 3. Any other approach I am not aware of.
GiteaMirror commented 2025-11-02 05:11:38 -06:00
Author
Owner
Copy Link

@lunny commented on GitHub (Nov 14, 2022):

Playing with the source code I find this functionality to be the same as the Wiki at the repository level. Adding all the needed code for the Org Wiki will duplicate code and functionality.

What will be the best approach?

  1. Reuse the code at the repository level and do any adjustment, if needed.
  2. Or, duplicate the wiki code at the Org level.
  3. Any other approach I am not aware of.

I think most code could be reused.

@lunny commented on GitHub (Nov 14, 2022): > Playing with the source code I find this functionality to be the same as the Wiki at the repository level. Adding all the needed code for the Org Wiki will duplicate code and functionality. > > What will be the best approach? > > 1. Reuse the code at the repository level and do any adjustment, if needed. > 2. Or, duplicate the wiki code at the Org level. > 3. Any other approach I am not aware of. I think most code could be reused.
GiteaMirror commented 2025-11-02 05:11:38 -06:00
Author
Owner
Copy Link

@louischopot commented on GitHub (Aug 7, 2023):

Any updates on this issue ?

@louischopot commented on GitHub (Aug 7, 2023): Any updates on this issue ?
GiteaMirror commented 2025-11-02 05:11:38 -06:00
Author
Owner
Copy Link

@erikhuck commented on GitHub (Aug 7, 2023):

@lunny @Xumeiquer @guillep2k Has there been any more progress on this since November 2022?

@erikhuck commented on GitHub (Aug 7, 2023): @lunny @Xumeiquer @guillep2k Has there been any more progress on this since November 2022?
GiteaMirror commented 2025-11-02 05:11:39 -06:00
Author
Owner
Copy Link

@Xumeiquer commented on GitHub (Aug 17, 2023):

I tried several times to do it, but without a guide on how to modify/improve the code without impacting on the Gitea design is hard, at least for me.

If someone can point me on the right direction I'll will try again.

@Xumeiquer commented on GitHub (Aug 17, 2023): I tried several times to do it, but without a guide on how to modify/improve the code without impacting on the Gitea design is hard, at least for me. If someone can point me on the right direction I'll will try again.
GiteaMirror commented 2025-11-02 05:11:39 -06:00
Author
Owner
Copy Link

@yp05327 commented on GitHub (Sep 17, 2024):

As we have implemented org level profile. Then we can use the same repo's wiki as the org's wiki?
Then the problem can be simple, adding a tab which links to this repo's wiki.

@yp05327 commented on GitHub (Sep 17, 2024): As we have implemented org level profile. Then we can use the same repo's wiki as the org's wiki? Then the problem can be simple, adding a tab which links to this repo's wiki.
GiteaMirror commented 2025-11-02 05:11:39 -06:00
Author
Owner
Copy Link

@msi-tl commented on GitHub (Oct 22, 2024):

I am really looking forward to this feature!

@msi-tl commented on GitHub (Oct 22, 2024): I am really looking forward to this feature!
GiteaMirror commented 2025-11-02 05:11:39 -06:00
Author
Owner
Copy Link

@wxiaoguang commented on GitHub (Dec 22, 2024):

Actually I see the easy and clear approach to do so, without touching the "wiki" code (just like yp05327 said)

It could be done like " Add Profile Readme for Organisations #27955 ": add a wiki in the "profile" repo, and show a tab (link) on the org's homepage.

Does it satisfy the requirement here?

@wxiaoguang commented on GitHub (Dec 22, 2024): Actually I see the easy and clear approach to do so, without touching the "wiki" code (just like yp05327 said) It could be done like " Add Profile Readme for Organisations #27955 ": add a wiki in the "profile" repo, and show a tab (link) on the org's homepage. Does it satisfy the requirement here?
GiteaMirror commented 2025-11-02 05:11:40 -06:00
Author
Owner
Copy Link

@wxiaoguang commented on GitHub (Dec 22, 2024):

-> Add profile wiki to org home #32947

easier than I thought

@wxiaoguang commented on GitHub (Dec 22, 2024): -> Add profile wiki to org home #32947 easier than I thought
GiteaMirror commented 2025-11-02 05:11:40 -06:00
Author
Owner
Copy Link

@wxiaoguang commented on GitHub (Mar 3, 2025):

-> Add profile wiki to org home #32947

easier than I thought

After more thinking, I think I will close #32947, because the layout would be quite complex and messy for different cases (public profile, private profile)

Actually, since we have "org profile readme" feature (#27955 and #32872), I think there is a pretty good workaround for this issue's case:

Org admin could create wiki under their "org profile" or "org private profile", and use org profile readme to describe it and link the wiki to org's home page. It is more flexible than hard-coded wiki link.

@wxiaoguang commented on GitHub (Mar 3, 2025): > -> Add profile wiki to org home [#32947](https://github.com/go-gitea/gitea/pull/32947) > > easier than I thought After more thinking, I think I will close #32947, because the layout would be quite complex and messy for different cases (public profile, private profile) ---- Actually, since we have "org profile readme" feature (#27955 and #32872), I think there is a pretty good workaround for this issue's case: Org admin could create wiki under their "org profile" or "org private profile", and use org profile readme to describe it and link the wiki to org's home page. It is more flexible than hard-coded wiki link.
GiteaMirror commented 2025-11-02 05:11:40 -06:00
Author
Owner
Copy Link

@GiteaBot commented on GitHub (Apr 3, 2025):

We close issues that need feedback from the author if there were no new comments for a month. 🍵

@GiteaBot commented on GitHub (Apr 3, 2025): We close issues that need feedback from the author if there were no new comments for a month. :tea:
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
$20
$250
$50
$500
backport/done
💎 Bounty
docs-update-needed
good first issue
hacktoberfest
issue/bounty
issue/confirmed
issue/critical
issue/duplicate
issue/needs-feedback
issue/not-a-bug
issue/regression
issue/stale
issue/workaround
lgtm/need 2
modifies/api
modifies/translation
outdated/backport/v1.18
outdated/theme/markdown
outdated/theme/timetracker
performance/bigrepo
performance/cpu
performance/memory
performance/speed
pr/breaking
proposal/accepted
proposal/rejected
pr/wip
pull-request
Mirrored from GitHub Pull Request
 reviewed/wontfix
💰 Rewarded
skip-changelog
status/blocked
topic/accessibility
topic/api
topic/authentication
topic/build
topic/code-linting
topic/commit-signing
topic/content-rendering
topic/deployment
topic/distribution
topic/federation
topic/gitea-actions
topic/issues
topic/lfs
topic/mobile
topic/moderation
topic/packages
topic/pr
topic/projects
topic/repo
topic/repo-migration
topic/security
topic/theme
topic/ui
topic/ui-interaction
topic/ux
topic/webhooks
topic/wiki
type/bug
type/deprecation
type/docs
type/enhancement
type/feature
type/miscellaneous
type/proposal
type/question
type/refactoring
type/summary
type/testing
type/upstream
No Label issue/needs-feedback issue/workaround type/feature type/proposal
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#3395
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?