Codeberg/Community
54
325
Fork
You've already forked Community
12

how to activate Issues in repo #2009

Closed
opened 2025年07月03日 08:26:43 +02:00 by Zolko · 3 comments

Comment

I forked a popular open-source software previously hosted on GitHub (FreeCAD), because the maintainers there refused to maintain an older version of that software, needed by some long-term projects (https://codeberg.org/Zolko/FreeCAD21). This is a regular repo and holds an "Issues" tab (https://codeberg.org/Zolko/FreeCAD21/issues)

On the advice of codeberg (Codeberg-e.V./requests#885) I created an umbrella organisation (xCAD) to hold that fork and share it with other developers. I then forked my FreeCAD21 repo into that account, but it remained to be presented as my fork. It also lacked an "Issues" tab.

I then transformed it into a regular repo which lost its status as a fork of my repo, hoping it would regain the "Issues" tab. Unfortunately, the repo (https://codeberg.org/xCAD/FreeCAD21) still doesn't have a "Issues" tab, which is very unfortunate.

Is there a way to have that forked-and-regularized repo (https://codeberg.org/xCAD/FreeCAD21) get all the usual features of a codeberg repository ?

I can also delete that repository and create a new empty one with all whistles-and-bells (https://codeberg.org/xCAD/test_issues) and re-upload my local repository. Is this the only way ?

### Comment I forked a popular open-source software previously hosted on GitHub (FreeCAD), because the maintainers there refused to maintain an older version of that software, needed by some long-term projects (https://codeberg.org/Zolko/FreeCAD21). This is a regular repo and holds an "Issues" tab (https://codeberg.org/Zolko/FreeCAD21/issues) On the advice of codeberg (https://codeberg.org/Codeberg-e.V./requests/issues/885) I created an umbrella organisation (xCAD) to hold that fork and share it with other developers. I then forked my FreeCAD21 repo into that account, but it remained to be presented as my fork. It also lacked an "Issues" tab. I then transformed it into a regular repo which lost its status as a fork of my repo, hoping it would regain the "Issues" tab. Unfortunately, the repo (https://codeberg.org/xCAD/FreeCAD21) still doesn't have a "Issues" tab, which is very unfortunate. Is there a way to have that forked-and-regularized repo (https://codeberg.org/xCAD/FreeCAD21) get all the usual features of a codeberg repository ? I can also delete that repository and create a new empty one with all whistles-and-bells (https://codeberg.org/xCAD/test_issues) and re-upload my local repository. Is this the only way ?

It's a fork, enable the repository unit

image

It's a fork, enable the repository unit ![image](/attachments/d4161459-7702-4b77-b5b3-4911099aee93)
141 KiB

If you're missing that tab:

click on your profile picture on the top right > Settings > Appearance

image

If you're missing that tab: click on your profile picture on the top right > Settings > Appearance ![image](/attachments/b67843cc-c296-4ae2-9c34-1538d75fd402)
Author
Copy link

@n0toose : thank-you, that did-it 👍

@n0toose : thank-you, that did-it 👍
Sign in to join this conversation.
No Branch/Tag specified
main
No results found.
Labels
Clear labels
accessibility

Reduces accessibility and is thus a "bug" for certain user groups on Codeberg.
bug

Something is not working the way it should. Does not concern outages.
bug
infrastructure

Errors evidently caused by infrastructure malfunctions or outages
Codeberg

This issue involves Codeberg's downstream modifications and settings and/or Codeberg's structures.
contributions welcome

Please join the discussion and consider contributing a PR!
docs

No bug, but an improvement to the docs or UI description will help
duplicate

This issue or pull request already exists
enhancement

New feature
infrastructure

Involves changes to the server setups, use `bug/infrastructure` for infrastructure-related user errors.
legal

An issue directly involving legal compliance
licence / ToS

involving questions about the ToS, especially licencing compliance
please chill
we are volunteers

Please consider editing your posts and remember that there is a human on the other side. We get that you are frustrated, but it's harder for us to help you this way.
public relations

Things related to Codeberg's external communication
question

More information is needed
question
user support

This issue contains a clearly stated problem. However, it is not clear whether we have to fix anything on Codeberg's end, but we're helping them fix it and/or find the cause.
s/Forgejo

Related to Forgejo. Please also check Forgejo's issue tracker.
s/Forgejo/migration

Migration related issues in Forgejo
s/Pages

Issues related to the Codeberg Pages feature
s/Weblate

Issue is related to the Weblate instance at https://translate.codeberg.org
s/Woodpecker

Woodpecker CI related issue
security

involves improvements to the sites security
service

Add a new service to the Codeberg ecosystem (instead of implementing into Gitea)
upstream

An open issue or pull request to an upstream repository to fix this issue (partially or completely) exists (i.e. Gitea, Forgejo, etc.)
wontfix

Codeberg's current set of contributors are not planning to spend time on delegating this issue.
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
Codeberg/Community#2009
Reference in a new issue
Codeberg/Community
No description provided.
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?