Closed awanlin closed 1 month ago
awanlin
commented
1 month ago Hi @04kash, could you run with this? Ideally we should try to follow the patterns from the main Backstage repo as much as we can. I might see if there is any other settings/config we should port over from there:
BethGriggs
commented
1 month ago Just want to cross-ref the latest comment from https://github.com/backstage/community-plugins/pull/1189
Based on discussion today in the SIG, I think we're going to implement a dashboard of some kind to track plugin requests even after they go stale or are ignored for >3 years. https://docs.google.com/document/d/1lIHXi8fi3CDiUD8UhX7s1FWCKAiricQKnFR4OSHoaiY/edit#heading=h.zkxxmxnsdv0
The idea is that we can keep issue numbers down, while still having a handle on all plugin requests.
nickboldt
commented
1 month ago decided to do something else here - close issues and then keep a main list of all the issues in one place.
📜 Description
The Stalebot should ignore issues related to new Plugin requests much like was done previously in the main Backstage repo:
https://github.com/backstage/backstage/blob/6dca65f95b398c809c23fc5dc5e24af63febe6b8/.github/workflows/automate_stale.yml#L31
👍 Expected behavior
Plugin request issues are ignored by the Stalebot
👎 Current Behavior
Plugin request issues are being marked as stale and closed by the Stalebot
👟 Reproduction steps
N/A
📃 Provide the context for the Bug.
This came up on Discord: https://discord.com/channels/687207715902193673/1282256196803231747
These requests really don't go stale until the plugin has been created.
👀 Have you spent some time to check if this bug has been raised before?
🏢 Have you read the Code of Conduct?
Are you willing to submit PR?
No, but I'm happy to collaborate on a PR with someone else