Search issues & pulls (eg via GH / lucene search syntax) #323

New Issue

noerw · 2021-01-12T16:51:47Z

noerw commented

2021-01-12 16:51:47 +00:00

Different options:

(a) as part of tea issues ls, or (b) in a new command tea issues search similar to repos
(a) using flags (--labels, --milestones...), or (b) using githubs search syntax (is:open author:norwin). The parser for this query syntax could be a part of code.gitea.io/sdk as this probably is a common use case.
- example parser

Personally I'd prefer variant 1-a, 2-b

Different options: 1. (a) as part of `tea issues ls`, or (b) in a new command `tea issues search` similar to repos 2. (a) using flags (`--labels`, `--milestones`...), or (b) using githubs search syntax (`is:open author:norwin`). The parser for this query syntax could be a part of code.gitea.io/sdk as this probably is a common use case. - [example parser](https://gitea.com/jolheiser/sip/src/branch/master/qualify/qualify.go) Personally I'd prefer variant 1-a, 2-b

noerw added the

kind

feature

label 2021-01-12 16:51:47 +00:00

6543 commented

2021-01-15 11:49:47 +00:00

Befor adding it to the sdk we could evolve it in tea and when its working nicely move it ...

👍 1

noerw added this to the v0.8.0 milestone 2021-03-12 11:53:55 +00:00

noerw referenced this issue

2021-06-25 12:48:03 +00:00

noerw commented

2021-06-25 12:52:35 +00:00

@jolheiser would you be fine if I include your qualify parser for this feature in tea, and we attribute it like the rest of the code as "© The Gitea Authors"?

@jolheiser would you be fine if I include your [qualify parser](https://gitea.com/jolheiser/sip/src/branch/master/qualify/qualify.go) for this feature in tea, and we attribute it like the rest of the code as "© The Gitea Authors"?

jolheiser commented

2021-06-25 14:11:20 +00:00

@jolheiser would you be fine if I include your qualify parser for this feature in tea, and we attribute it like the rest of the code as "© The Gitea Authors"?

That's fine with me. Although, a few things come to mind.

That code is a bit old and could probably do with a cleanup/refactor
Perhaps a separate package altogether?
- That way you could make it more extensible (e.g. you wanted variants for a-1 vs a:1)
- It could be used by both projects (if I have time to get back to sip, that is...)
- Could possibly be used in Gitea itself if we want to implement it there

> @jolheiser would you be fine if I include your [qualify parser](https://gitea.com/jolheiser/sip/src/branch/master/qualify/qualify.go) for this feature in tea, and we attribute it like the rest of the code as "© The Gitea Authors"? That's fine with me. Although, a few things come to mind. 1. That code is a bit old and could probably do with a cleanup/refactor 2. Perhaps a separate package altogether? * That way you could make it more extensible (e.g. you wanted variants for `a-1` vs `a:1`) * It could be used by both projects (if I have time to get back to sip, that is...) * Could possibly be used in Gitea itself if we want to implement it there

👍 1

noerw referenced this issue

2021-07-01 07:28:51 +00:00

Add more issue filters when go-sdk >=1.15 #376

6543 referenced this issue from gitea/go-sdk

2021-08-12 15:02:38 +00:00

`tea issues list` add filter for milestone #535

6543 modified the milestone from v0.8.0 to v0.9.0

2021-08-16 12:54:28 +00:00

noerw referenced this issue

2021-09-14 10:07:56 +00:00

Implement more issue filters #400