Labels
Something is not working codeberg
This issue is specific to Codeberg's downstream modifications or settings and must be addressed here contribution 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 gitea-related
Likely involves Gitea change, please also check Gitea's issue tracker infrastructure
Involves changes to the server setups invalid
Something is wrong legal
An issue directly involving legal compliance licence / ToS
involving questions about the ToS, especially licencing compliance pages
Issues related to the Codeberg Pages feature public relations
Things related to Codeberg's external communication question
More information is needed security
involves improvements to the sites security service
Add a new service to the Codeberg ecosystem (instead of implementing into Gitea) upstream
This issue is reported upstream wontfix
This won't be fixed
Apply labels
Clear labels
bug
Something is not working codeberg
This issue is specific to Codeberg's downstream modifications or settings and must be addressed here contribution 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 gitea-related
Likely involves Gitea change, please also check Gitea's issue tracker infrastructure
Involves changes to the server setups invalid
Something is wrong legal
An issue directly involving legal compliance licence / ToS
involving questions about the ToS, especially licencing compliance pages
Issues related to the Codeberg Pages feature public relations
Things related to Codeberg's external communication question
More information is needed security
involves improvements to the sites security service
Add a new service to the Codeberg ecosystem (instead of implementing into Gitea) upstream
This issue is reported upstream wontfix
This won't be fixed
No Label
bug
codeberg
contribution welcome
docs
duplicate
enhancement
gitea-related
infrastructure
invalid
legal
licence / ToS
pages
public relations
question
security
service
upstream
wontfix
Milestone
Set milestone
Clear milestone
No items
No Milestone
Assignees
Assign users
Clear assignees
No Assignees
3 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.
No due date set.
Blocks
#587 button for plain md files
Codeberg/Community
#402 Search for repos in particular language
Codeberg/Community
#280 FR: Add RSS feed to projects
Codeberg/Community
#217 Code browser: HTTP code 404 when I click on a submodule directory which is the wiki repository of the project
Codeberg/Community
#190 Directory listing on mobile is not really compact.
Codeberg/Community
Reference in new issue
There is no content yet.
Delete Branch '%!s(MISSING)'
Deleting a branch is permanent. It CANNOT be undone. Continue?
No
Yes
This issue is a summary of issues that will be fixed in the Gitea version 1.17.0
Fixes #217
Fixes #280
Fixes #402
Fixes #190
Did the milestone not work out?
I think the issue is better since we can close all relating issues by adding:
in the comment above
or do we need to submit a new comment for the detection to work
this only says referenced but not will be closed by
I think the auto-closing only works with pull requests.
huh then it wouldnt matter...
what are the dependencies for?
Well, it was easier for me to just type "1.17" into the search box in an issue, rather than editing or mentioning it here in a comment. Also, the logic makes more sense - the issue can only be closed after the Gitea deployment issue was closed.
makes sense but there is no way of auto close all related issues is it?
but that means that issues make more sense than milestones because after adding the summary issue as a dependency youre not able to close the issue early
Welp, due to a mysterious issue. Adding a comment here instead, fixes #587