Gitea v1.17 #579
Labels
No labels
accessibility
bug
bug
infrastructure
Codeberg
contributions welcome
docs
duplicate
enhancement
infrastructure
legal
licence / ToS
please chill
we are volunteers
public relations
question
question
user support
s/Forgejo
s/Forgejo/migration
s/Pages
s/Weblate
s/Woodpecker
security
service
upstream
wontfix
No milestone
No project
No assignees
3 participants
Notifications
Due date
No due date set.
Blocks
#190 Directory listing on mobile is not really compact.
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
#236 Notifications about new followers
Codeberg/Community
#280 FR: Add RSS feed to projects
Codeberg/Community
#402 Search for repos in particular language
Codeberg/Community
#587 button for plain md files
Codeberg/Community
Reference
Codeberg/Community#579
Loading…
Add table
Add a link
Reference in a new issue
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?
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
Fixes #645
Fixes #533
Fixes #612
Fixes #600
Fixes #587
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