Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

avoid posting related topics on empty issues, and close them #37

Open
jba opened this issue Oct 7, 2024 · 3 comments
Open

avoid posting related topics on empty issues, and close them #37

jba opened this issue Oct 7, 2024 · 3 comments

Comments

@jba
Copy link
Contributor

jba commented Oct 7, 2024

https://go.dev/issue/69795 was posted with an empty issue body. Gaby should close such issues.
Instead it posted a "related issues" comment (which included other empty issues—good job there).

@hyangah
Copy link
Contributor

hyangah commented Nov 20, 2024

another approach (from @ianthehat) is to let LLM classify as part of gaby's regular labeling task, and don't trigger related topics / summary posting.

@hyangah
Copy link
Contributor

hyangah commented Dec 13, 2024

Another thought while reviewing CL 645875:

We are doing markdown parsing. If the contents have only headings and the contents after removing headings are little, it's likely a spam or empty.

Another floating idea:

If the similarity search finds only issues with "empty" or "invalid" label, we can assume it is similarly empty or invalid. (depending on which LLM call is cheaper)

@gopherbot
Copy link
Contributor

Change https://go.dev/cl/636875 mentions this issue: internal/labels: check for empty issue

gopherbot pushed a commit that referenced this issue Dec 17, 2024
If an issue has no text other than headings, label it invalid.

For #37.

Change-Id: I8ba7c0f9708efd302d1a318553a403e00fbdad3f
Reviewed-on: https://go-review.googlesource.com/c/oscar/+/636875
LUCI-TryBot-Result: Go LUCI <golang-scoped@luci-project-accounts.iam.gserviceaccount.com>
Reviewed-by: Hyang-Ah Hana Kim <hyangah@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants