8000 feat: Setup Stale workflow by Panquesito7 · Pull Request #524 · devicons/devicon · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

feat: Setup Stale workflow #524

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

Merged
merged 6 commits into from
Mar 8, 2021
Merged

Conversation

Panquesito7
Copy link
Member
@Panquesito7 Panquesito7 commented Mar 3, 2021

Things added/changed:

  • Configure/setup Stale workflow.

@Panquesito7 Panquesito7 added the devops Use this label for devops related enhancements label Mar 3, 2021
@Thomas-Boi
Copy link
Member

Hey @Panquesito7,

What is the Probot Stale app? Based on what I've seen, it leaves a comment on PRs/Issues that are stale right?

For Devicon, we unfortunately accumulate a lot of stale issues. These are features/bugs that we haven't have time to get around fixing but we will do it eventually. I'm debating whether we need this bot since our use case is very specific.

Same for the PR as well. A few of them need to be split up into smaller PRs which will be done once we get around to it.

@Panquesito7 Panquesito7 added the discussion Use this label for community discussions about changes/features/.. label Mar 3, 2021
@Panquesito7
Copy link
Member Author

What is the Probot Stale app?

After 30 days (or a specific period of time), it will mark a PR/issue as stale. It will post a comment (customizable) saying that the PR/issue is stale/abandoned now. I copied the message you send on a stale PR.

I think this will be useful for PRs that have been there a long time opened. The PR/issue won't be closed automatically unless specified. Let's see what @amacado thinks about this. 🙂

@amacado
Copy link
Member
amacado commented Mar 3, 2021

Hello! My first thought was: "Great idea", but when I think about it longer, I follow the thought of @Thomas-Boi. In my opinion we would have to distinguish between Pull-Requests and Issues.

For pull requests a stale label makes sense, but in our case, tracking icon requests via issues, they are never "stale" in my understanding, but only "pending". So auto-labeling them as stale could be offending.

I don't see an option in the https://github.com/marketplace/stale bot to distingush between pull requests and issues, so this might not be the best fit for our project.

@Panquesito7
Copy link
Member Author

It would be nice if we could apply this only for PRs...
What about this workflow? Looks like it's what we were looking for.

Tell me what do you think. 🙂

@Thomas-Boi
Copy link
Member

It would be nice if we could apply this only for PRs...
What about this workflow? Looks like it's what we were looking for.

Tell me what do you think. 🙂

This action seems better suited for us. I'm down for us using this one 👍

@Panquesito7 Panquesito7 force-pushed the panquesito7/add/probot-stale branch from ca392c7 to 4bb713d Compare March 4, 2021 19:14
@Panquesito7 Panquesito7 changed the title feat: Setup Probot Stale app feat: Setup Stale workflow Mar 4, 2021
Copy link
Member Author
@Panquesito7 Panquesito7 left a comment

Choose a reason for hiding this comment

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

Updated. Please review if it looks OK. 🙂

Copy link
Member
@amacado amacado left a comment

Choose a reason for hiding this comment

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

I think it would be a good idea to have a note in our https://github.com/devicons/devicon/blob/master/CONTRIBUTING.md guidelines to inform about this action and what it does?

Thomas-Boi
Thomas-Boi previously approved these changes Mar 7, 2021
Copy link
Member
@Thomas-Boi Thomas-Boi left a comment

Choose a reason for hiding this comment

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

Hey @Panquesito7 ,

This PR looks good. I think you only need to update the README.md and everything should be good to go.

@Panquesito7 Panquesito7 force-pushed the panquesito7/add/probot-stale branch from 01b86b1 to ded0713 Compare March 7, 2021 21:30
Co-authored-by: Clemens Bastian <amacado@users.noreply.github.com>
Copy link
Member
@amacado amacado left a comment

Choose a reason for hiding this comment

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

I (hope) i fixed some spelling issues in the text. I'm not sure with the linebreaks, so someone should test this before going live..

@amacado amacado removed the approved label Mar 8, 2021
@Panquesito7
Copy link
Member Author

so someone should test this before going live...

If there are errors in the workflow syntax, it would display an error. For example, see this run (it has been already fixed).

Co-authored-by: Clemens Bastian <amacado@users.noreply.github.com>
@Panquesito7 Panquesito7 requested a review from amacado March 8, 2021 19:01
@Panquesito7 Panquesito7 merged commit 2e041e2 into develop Mar 8, 2021
@Panquesito7 Panquesito7 deleted the panquesito7/add/probot-stale branch March 8, 2021 20:04
GCHQDeveloper926 pushed a commit to GCHQDeveloper926/devicon that referenced this pull request Dec 20, 2024
* feat: Setup Stale workflow

* Change stale pull request message

Thanks, @Thomas-Boi!

* Add a note on `README.md` about stale PRs

* Fix some issues with the workflow

* Apply suggestions from code review

Co-authored-by: Clemens Bastian <amacado@users.noreply.github.com>

* Apply suggestions from code review

Co-authored-by: Clemens Bastian <amacado@users.noreply.github.com>

Co-authored-by: Clemens Bastian <amacado@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
devops Use this label for devops related enhancements discussion Use this label for community discussions about changes/features/..
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants
0