Conversation
Engineers now have access to close publish issues directly, making the #retract comment command redundant. This removes the workflow, module, entry point, tests, and documentation for the feature.
|
@BYK FYI we still have this in our issue template (example):
Also, this was actually useful for contractors, because they cannot retract issues (no permissions to close issues). How should this be handled? :) |
|
@christophaigner you still have it in your issue template as you have not updated your create release action 😀 I'm fine bringing it back if it adds value, have not thought about contractor case. |
|
@BYK ah, well that makes sense 😄 I think it'd be great to bring it back, that's probably the easiest way to handle this scenario :) Thank you! 🙏🏻 |
|
@BYK is it just this PR that needs to be reverted? Could you please revert it? :) |
This reverts commit 89f6457.
2 participants
Summary
#retractcomment command — engineers now have direct access to close publish issues themselves, making this feature redundant.Changes
Deleted:
.github/workflows/retract.yml— workflow that listened for#retractcommentssrc/modules/retract-release.js— core retract logic (post comment + close issue)src/publish/retract.js— GitHub Actions entry pointsrc/modules/__tests__/retract-release.js— testsEdited:
README.md— removed the#retractflowchart branch and the "Retracting Release Request" sectionsrc/modules/__tests__/update-issue.js— removed#retractinstruction from test fixture strings