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.

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

x/build/cmd/gopherbot: follow-up backport comments are ignored #25574

Open
andybons opened this issue May 25, 2018 · 6 comments
Open

x/build/cmd/gopherbot: follow-up backport comments are ignored #25574

andybons opened this issue May 25, 2018 · 6 comments
Labels
Builders x/build issues (builders, bots, dashboards) Friction Nuisances that make good candidates for our "friction" fix-it weeks help wanted NeedsFix The path to resolution is known, but the work has not been done.
Milestone
Unplanned

Comments

@andybons
Copy link
Member

In #25242 (comment) I ask for gopherbot to create a backport for 1.9 as well (the original backport was only for 1.10). But an issue was not created (had to create it manually).

/cc @FiloSottile
@andybons andybons added the NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. label May 25, 2018
@andybons andybons added this to the Unplanned milestone May 25, 2018
@gopherbot gopherbot added the Builders x/build issues (builders, bots, dashboards) label May 25, 2018
@FiloSottile FiloSottile mentioned this issue Jun 15, 2018
Closed
@andybons
Copy link
Member Author

@gopherbot please remove needsinvestigation and add needsfix

@gopherbot gopherbot added NeedsFix The path to resolution is known, but the work has not been done. and removed NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. labels Jun 20, 2018
@FiloSottile FiloSottile mentioned this issue Aug 31, 2018
Closed
@dmitshur dmitshur mentioned this issue Nov 13, 2018
Closed
@dmitshur
Copy link
Contributor

Also happened in #28688 (comment).

@dmitshur dmitshur mentioned this issue Mar 21, 2019
Closed
@dmitshur
Copy link
Contributor

Happened again in #30374 (comment), @jayconrod had to create the backport issue manually.

@dmitshur dmitshur mentioned this issue Mar 21, 2019
Closed
@bcmills
Copy link
Contributor

bcmills commented May 7, 2019

One more in #29591.

@dmitshur
Copy link
Contributor

dmitshur commented Oct 2, 2019 •
edited
Loading

Another in #34364 (comment).

One more in #36101 (comment). /cc @aclements

Another in #39817 (comment). /cc @FiloSottile

@dmitshur dmitshur mentioned this issue Oct 2, 2019
Closed
@jayconrod
Copy link
Contributor

Another in #36568.

@aclements aclements mentioned this issue Aug 20, 2020
Closed
@dmitshur dmitshur mentioned this issue Sep 10, 2020
Closed
@dmitshur dmitshur mentioned this issue Nov 13, 2020
Closed
This was referenced Mar 8, 2021
Closed
Closed
@prattmic prattmic mentioned this issue Aug 13, 2021
Closed
@dmitshur dmitshur mentioned this issue Dec 21, 2022
Closed
@dmitshur dmitshur mentioned this issue Aug 3, 2023
Closed
@dmitshur dmitshur mentioned this issue Feb 2, 2024
Closed
@dmitshur dmitshur mentioned this issue Oct 2, 2024
Closed
@dmitshur dmitshur added the Friction Nuisances that make good candidates for our "friction" fix-it weeks label Oct 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Builders x/build issues (builders, bots, dashboards) Friction Nuisances that make good candidates for our "friction" fix-it weeks help wanted NeedsFix The path to resolution is known, but the work has not been done.
Projects
None yet
Milestone
Unplanned
Development

No branches or pull requests
5 participants
@jayconrod @andybons @dmitshur @bcmills @gopherbot