pending release label remains after issues are closed
See original GitHub issueCurrently, we have to manually remove pending release
from an issue whenever it’s closed, would be nice if we can have GitHub automatically remove pending release
label from an issue when it’s closed. https://github.com/Automattic/mongoose/issues/9672#event-4081686498 is an example of an issue opened due to thinking that a feature wasn’t released even though it’s released in v5.9.0.
Another option would to not use pending release
altogether and work with open/closed issues.
Issue Analytics
- State:
- Created 3 years ago
- Comments:5
Top Results From Across the Web
Configure label to be removed when issue is closed. - GitLab
Problem When an issue is closed, its most recent workflow label is not removed ... This is still pending some solution from our...
Read more >Using Label Policy Rules to Troubleshoot Label Issues
If the policy shows Pending status, you should wait until its successfully distributed. Labels, label policies and label policy rules can also ...
Read more >How to Complete Orders if Your Shop is Closed or Suspended
Before refunding an order, use Etsy Messages to let the buyer that you can't complete their transaction. Once you issue the refund, Etsy...
Read more >Troubleshooting Missing or Disappearing Print Jobs - PaperCut
Look for the held print job in the PaperCut Admin interface under Printers → Jobs Pending Release. Does the username match what you...
Read more >About open vs. pending and on-hold tickets - Zendesk help
This closed loop process is important for both your company and your customers; it puts you both on the same page - an...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Thanks for your help @AbdelrahmanHafez . I think the approach of not using the “Pending Release” label at all is the way to go. You’re right that a dangling “Pending Release” label can cause lasting confusion, whereas an issue being closed but not released yet is only temporary. We’ll get rid of this label 👍
Okay, I think that would work if we could still use them for major releases.
In which case I think we should just close this issue.