Gitea v1.17 #579

Closed
opened 2022-02-08 19:53:06 +01:00 by resectio · 9 comments
Image

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

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
Image
Owner

Did the milestone not work out?

Did the milestone not work out?
Image
Author

I think the issue is better since we can close all relating issues by adding:

Fixes #123

in the comment above

I think the issue is better since we can close all relating issues by adding: ``` Fixes #123 ``` in the comment above
Image
Author

or do we need to submit a new comment for the detection to work

image

this only says referenced but not will be closed by

or do we need to submit a new comment for the detection to work ![image](/attachments/acb627bb-a57c-4b4e-8c62-f20dafb7b804) this only says referenced but not will be closed by
7.6 KiB
Image
Owner

I think the auto-closing only works with pull requests.

I think the auto-closing only works with pull requests.
Image
Author

huh then it wouldnt matter...

what are the dependencies for?

huh then it wouldnt matter... what are the dependencies for?
Image
Owner

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.

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.
Image
Author

makes sense but there is no way of auto close all related issues is it?

makes sense but there is no way of auto close all related issues is it?
Image
Author

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.

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

> 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. 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
Image
Owner

Welp, due to a mysterious issue. Adding a comment here instead, fixes #587

~~Welp, due to a [mysterious issue](https://github.com/go-gitea/gitea/issues/19368). Adding a comment here instead, fixes #587~~
Image 6543 closed this issue 2022-08-09 14:19:10 +02:00
Sign in to join this conversation.
No milestone
No project
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.

Reference
Codeberg/Community#579
No description provided.