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

stale-bot config #6495

Closed
wants to merge 1 commit into from
Closed

stale-bot config #6495

wants to merge 1 commit into from

Conversation

jsquyres
Copy link
Member

Initial configuration for the Probot stale bot:
https://github.com/probot/stale.

Signed-off-by: Jeff Squyres jsquyres@cisco.com

Initial configuration for the Probot stale bot:
https://github.com/probot/stale.

Signed-off-by: Jeff Squyres <jsquyres@cisco.com>
@jsquyres
Copy link
Member Author

Proposal to discuss at the 2019-03-19 webex: Probot stale bot (https://github.com/probot/stale). The config options I put in here are just the starting point for a discussion.

PROs:

  • Auto-close all those issues that, realistically, we won't get to
  • Put a label on them to easily find them again someday, if needed

CONs:

  • This would take effect of all of our old issues and/or PRs (can't limit it to just "new" issues to try it out)

NOTE: I initially proposed the "lock" bot at the RM meeting on 2019-03-18 (https://probot.github.io/apps/lock/), without realizing that it actually prevents any further discussion on an issue/PR (i.e., it locks them). The lock bot allows selectively applying to issues/PRs after a certain date. This one -- the stale bot -- does not: it would apply to all of our open issues/PRs.

If we want to start using the the stale bot, we might want to manually do something about all of our old/stale bugs before enabling it.

@gpaulsen gpaulsen added this to the v4.0.1 milestone Mar 18, 2019
@jsquyres
Copy link
Member Author

Put out for comment on the OMPI dev list: https://www.mail-archive.com/devel@lists.open-mpi.org/msg20868.html

@jsquyres jsquyres removed this from the v4.0.1 milestone Mar 25, 2019
@jsquyres
Copy link
Member Author

It looks like we're leaning towards running this bot on our own node.js server (e.g., on aws.open-mpi.org). One of the OMPI organizations may be able to provide a resource to actually get this done within the next month or so.

There's no real rush on this, so let's wait until that resource becomes available.

@gpaulsen
Copy link
Member

gpaulsen commented Apr 2, 2019

As discussed in today's web-ex, Brian has created a wiki for Bot tasks for this summer:

@lanl-ompi
Copy link
Contributor

Can one of the admins verify this patch?

@jsquyres
Copy link
Member Author

@bwbarrett Did we decide not to do the stale bot? Or was this just waiting for us to set up our own probot instance?

@lrbison
Copy link
Contributor

lrbison commented Feb 21, 2024

🧟 I think this one is OBE by #12329, can we close it?

@jsquyres jsquyres closed this Feb 21, 2024
@jsquyres jsquyres deleted the pr/stale-bot branch February 21, 2024 14:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants