Skip to content

maintenance: investigate why gopherbot didn't auto-close some issues #1292

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.

Sign up for GitHub

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

Jump to bottom
Closed
hyangah opened this issue Mar 11, 2021 · 1 comment
Closed

maintenance: investigate why gopherbot didn't auto-close some issues #1292

hyangah opened this issue Mar 11, 2021 · 1 comment
Assignees
@dmitshur @hyangah
Labels
FrozenDueToAge
Milestone
vscode-go/unplanned

Comments

@hyangah
Copy link
Contributor

hyangah commented Mar 11, 2021

Gopherbot should close issues labeled with WaitingForInfo after 30days.
But we observed some issues weren't closed as expected.
https://github.com/golang/build/blob/d1ab7ac8e2c8abfb70534c7c684d493f8e053f0a/cmd/gopherbot/gopherbot.go#L1002
Investigate and fix the issue.
@gopherbot gopherbot added this to the Untriaged milestone Apr 8, 2021
@stamblerre stamblerre modified the milestones: Untriaged, Backlog Apr 9, 2021
@hyangah
Copy link
Contributor Author

hyangah commented Apr 15, 2022

This is fixed in golang/go#52017

@hyangah hyangah closed this as completed Apr 15, 2022
@golang golang locked and limited conversation to collaborators Apr 15, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@dmitshur dmitshur

@hyangah hyangah

Labels
FrozenDueToAge
Projects
None yet
Milestone
vscode-go/unplanned
Development

No branches or pull requests
4 participants
@dmitshur @hyangah @stamblerre @gopherbot