Display confirmation box when closing an issue with a comment
See original GitHub issueUseful to avoid accidentally closing issues.
Should be applied for all issue pages: https://github.com/*/*/issues/*
Should be triggered when clicking this button:
Issue Analytics
- State:
- Created 3 years ago
- Reactions:1
- Comments:9 (8 by maintainers)
Top Results From Across the Web
Custom confirm box that has some functionality to it with ...
To display a confirm box when closing the window, you can use the onbeforeunload event. This will ask the user if they wish...
Read more >Display confirmation popup whenever trying to submit a issue ...
which displays a confirmation popup whenever trying to submit a new issue or comment via Ctrl+Enter or Enter , but it's too simple...
Read more >JavaScript Message Boxes: alert(), confirm(), prompt()
The alert() function displays a message to the user to display some information to users. This alert box will have the OK button...
Read more >Add a confirmation dialog display on the Click of Cancel Button
Add a confirmation dialog display on the Click of Cancel Button ... I click the back button to return to the issue and...
Read more >Confirmation popup on close incident. - ServiceNow Community
As an ESS / ITIL user (legacy view and Portal View) for Incidents and Service Requests, Problem. Once i click on Close UI...
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 FreeTop 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
Top GitHub Comments
In some cases, closing an issue accidentally can have unintended consequences, such as triggering (the start or end of) different github actions. It can also lead to confusion among PR reviewers, especially if GH events are pushed to some external source (slack channels, etc).
@fregante would it be possible to re-open this issue?
Given the non-destructiveness of the action I don’t think it’s worth messing with that. That button already has enough logic behind it (and more is coming with #3881)