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

Add/tweak probots configuration. #56884

Merged
merged 1 commit into from
Jan 6, 2019
Merged

Add/tweak probots configuration. #56884

merged 1 commit into from
Jan 6, 2019

Conversation

MikeMcQuaid
Copy link
Member

This adds the other probots used by the other Homebrew taps and tweaks the
existing configuration to be consistent with the other Homebrew taps.

Feel free to disagree on any of the individual changes, I am very open to
discussion.

Once these are all addressed and this is merged I will open the agreed version
on all the other Cask taps.

@vitorgalvao
Copy link
Member

There’s a stray commit for mkvtoolnix-app.

@@ -10,6 +10,6 @@ lockComment: false
# Limit to only `issues` or `pulls`
# only: issues
# Add a label when locking. Set to `false` to disable
lockLabel: false
lockLabel: outdated
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why the label? Seems to me locking as “resolved” should be sufficient.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@vitorgalvao It makes it easier to quickly query for locked issues which have other labels.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It makes it easier to quickly query for locked issues which have other labels.

Can't you just search for the other labels then?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That doesn't allow differentiation between locked/not locked or autolocked/not autolocked from the search interface.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For the sake of getting this merged can you agree whether this is blocking or not?

.github/no-response.yml Outdated Show resolved Hide resolved
.github/support.yml Outdated Show resolved Hide resolved
@MikeMcQuaid
Copy link
Member Author

Updated based on comments.

@vitorgalvao
Copy link
Member

@MikeMcQuaid Mind removing https://github.com/Homebrew/homebrew-cask/blob/master/.github/no-response.yml?

stale makes that one redundant, and I never liked it much anyway (doesn’t close PRs, only issues).

@MikeMcQuaid
Copy link
Member Author

@MikeMcQuaid Mind removing https://github.com/Homebrew/homebrew-cask/blob/master/.github/no-response.yml?

stale makes that one redundant, and I never liked it much anyway (doesn’t close PRs, only issues).

@vitorgalvao I'd rather it's left to be consistent with other repos. I think it's a useful pattern to be able to adjust that separately.

@MikeMcQuaid MikeMcQuaid merged commit a8ca2de into Homebrew:master Jan 6, 2019
@vitorgalvao
Copy link
Member

I'd rather it's left to be consistent with other repos.

Why do other repos have that, though?

I don’t think anyone in HBC particularly likes that bot. In fact, I’ll go so far as to say it’s outright useless for us, as it never acts. Issues never get the label because either:

  1. The template was filled, so we already got what we need.
  2. The template was not filled, so the issue is closed.

And the only place where we do need it (PRs), it does nothing. The only reason that bot was still active was in the hopes it eventually supported our use case (PRs). Since we’re adding the stale bot, no-response can go.

# Assign `resolved` as the reason for locking. Set to `false` to disable
setLockReason: false
setLockReason: resolved
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is causing an error in all repos. Looks like it needs to be a boolean (even though they still have that resolved comment in their example).

Also, @MikeMcQuaid, note you don’t need to PR every repo to sync these settings, we have a script for it.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@vitorgalvao Where is the error?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@MikeMcQuaid The bot’s opening issues: #57088

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@vitorgalvao Sorry about that, will fix.

@MikeMcQuaid MikeMcQuaid deleted the probots branch January 6, 2019 16:24
@MikeMcQuaid
Copy link
Member Author

Why do other repos have that, though?

If we're awaiting a reply from a user an an open issue to provide more information than is in the template i.e. is issue-specific.

@dessant
Copy link

dessant commented Jan 8, 2019

Make sure to put the label name in quotes if it contains spaces, otherwise config parsing will fail:
https://github.com/Homebrew/homebrew-cask/blob/master/.github/support.yml#L4

@MikeMcQuaid
Copy link
Member Author

Thanks @dessant!

@vitorgalvao opened #57222 and Homebrew/homebrew-cask-versions#6821, sorry for the delay.

@lock lock bot added the outdated label Feb 8, 2019
@lock lock bot locked as resolved and limited conversation to collaborators Feb 8, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants