Illya Marchenko

> Also after this: > > https://github.com/go-gitea/gitea/blob/f4920c9c7f5947d3b6476610f39bc3492ab4ef3b/models/migrations/migrations.go#L469 Done!

> Your functions should actually be in a new file `v245.go`, don't modify old migrations Good point! Done

> I agree with @jolheiser's comment on [#23113 (comment)](https://github.com/go-gitea/gitea/pull/23113#issuecomment-1444098901). > > I don't fully understand the value of this feature either. To clarify, I don't believe it's entirely useless, but...

> Maybe we need a better sidebar design, there are too items for time. I'd would love to work on new time tracking/estimate ui in the next pr, since I...

What are current problems with preview tab? We use it. At least, if not features are supported, they can be disabled for preview. But it's essential for formatting an issue

> I see. If some organization labels are same to the repo labels, then we need something like priority to avoid displaying same label twice. This is a good issue....

> That comment is about 4 month ago, and I want to update my comment. > > Instead of hiding same labels, I think we can: > > * avoid...

> if organization has same label with repo, i will not be able to know which label is repo's label. currect order is repo labels then org labels, so i...

> After reconsidered about this issue, I think we need to avoid creating duplicate labels, as this doesn't make sense. I guess the implementation of org labels was just copy-paste,...

> > I just want to make one point. after this change, if organization has same label with repo, i will not be able to know which label is repo's...