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

create configuration file for probot-stale #1360

Merged
merged 2 commits into from
May 1, 2017
Merged

create configuration file for probot-stale #1360

merged 2 commits into from
May 1, 2017

Conversation

waldyrious
Copy link
Member

So this is my proposal for configurations to use in our probot-stale integration, as discussed in #1350.

Any feedback about the time periods, messages, or other details of the configuration? /cc @agnivade @Ostera @jeeftor @sbrl @igorshubovych @rubenvereecken.

Note: merging this won't automatically enable probot-stale on this repo; we'll need to activate it in https://github.com/integration/probot-stale.

Copy link
Member

@agnivade agnivade left a comment

Choose a reason for hiding this comment

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

Looks good overall. Just some minor comments.

# Configuration for probot-stale - https://github.com/probot/stale

# Number of days of inactivity before an issue or PR is considered stale
daysUntilStale: 30
Copy link
Member

Choose a reason for hiding this comment

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

I would tune it down to 15

Copy link
Member Author

Choose a reason for hiding this comment

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

Sure.

# Comment to post when marking an issue or PR as stale
markComment: >
Hi all! This thread has not had any recent activity.
Can anyone comment on what's blocking progress?
Copy link
Member

Choose a reason for hiding this comment

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

This line feels a bit weird. I would rather change it to "Any updates on this ?'

Copy link
Member Author

Choose a reason for hiding this comment

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

How about "Are there any updates?"

What I like about the initial version is that it makes a specific call to action rather than placing a generic question. But it's not a big deal, and we can tweak the message later if we can find a way to combine the advantages of both sentences.

Copy link
Member

Choose a reason for hiding this comment

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

How about "Are there any updates?"

looks good.

Copy link
Member Author

Choose a reason for hiding this comment

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

Any comments on the call to action part?

Copy link
Member

Choose a reason for hiding this comment

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

I mean I don't see that the new version is not a call to action in any way. Its not direct, that's true. And I would rather not be too direct. The new version seems to have the right tonality and still ask for some work to be done in a friendly way.

Copy link
Member Author

Choose a reason for hiding this comment

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

Ok, I can see that.

daysUntilStale: 30

# Number of days of inactivity before a stale issue or PR is closed
daysUntilClose: 30
Copy link
Member

Choose a reason for hiding this comment

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

Is this absolute, or days after daysUntilStale?

Copy link
Member

Choose a reason for hiding this comment

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

The later. Its mentioned before a stale issue

@agnivade
Copy link
Member

agnivade commented Apr 30, 2017

I have a question though. Lets say a PR becomes stale, the bot marks it as such. Then someone comments on it. Will the bot remove the label "stale" ?

Logic suggests that it should, otherwise it doesn't make sense that when the PR becomes stale again for the 2nd time, it can't re-label something when its already labelled.

@waldyrious
Copy link
Member Author

@agnivade yes, it does remove the label -- the example I pointed out in #1350 shows this in action:

  • probot-stale bot added the wontfix label 24 days ago
  • probot-stale bot commented 24 days ago: "This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions."
  • TheLastProject commented 24 days ago: "Seriously? That's a horrible way to manage issues. In that case: bump (because you're forcing me to)"
  • probot-stale bot removed the wontfix label 24 days ago

@waldyrious
Copy link
Member Author

I made the requested changes, @agnivade & @sbrl -- please review :)

@waldyrious waldyrious added the tooling Helper tools, scripts and automated processes. label May 1, 2017
Copy link
Member

@agnivade agnivade left a comment

Choose a reason for hiding this comment

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

Looks good ! Waiting to see this go live !

@waldyrious
Copy link
Member Author

Alright! let's try this out :)

@waldyrious waldyrious merged commit 90f24d0 into master May 1, 2017
@waldyrious waldyrious deleted the probot-stale branch May 1, 2017 15:22
@waldyrious
Copy link
Member Author

Ok, this is now installed, as can be confirmed in https://github.com/organizations/tldr-pages/settings/installations. Let's see how it goes.

@sbrl
Copy link
Member

sbrl commented May 2, 2017

So this just works? We don't need to add the functionality to the upcoming bot for this?

@waldyrious
Copy link
Member Author

Not if the way this works is sufficient for our needs :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
tooling Helper tools, scripts and automated processes.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants