Gitea v1.17 #579

Open
opened 4 months ago by schorsch · 9 comments
Collaborator

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

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
Daniellop added the
gitea-related
label 4 months ago
Collaborator

Did the milestone not work out?

Did the milestone not work out?
Poster
Collaborator

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
Poster
Collaborator

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
Collaborator

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

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

huh then it wouldnt matter...

what are the dependencies for?

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

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.
Poster
Collaborator

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?
Poster
Collaborator

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
schorsch added a new dependency 2 months ago
Collaborator

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~~
Gusted added a new dependency 3 weeks ago
Gusted removed a dependency 3 weeks ago
Gusted added a new dependency 3 weeks ago
Sign in to join this conversation.
No Milestone
No Assignees
3 Participants
Notifications
Due Date

No due date set.

Loading…
There is no content yet.