Repository navigation
feat: allow to acknowledge pullrequest - #349
Conversation
A 204 has no JSON to decode, so response.json() rejected and a successful change looked like a failure.
apiFetch gains signInOnUnauthorized (default true). An action the viewer triggered can pass false to show an inline message and a Sign in button instead of leaving the page for the login mid click. currentReturnTo is exported so that button can return to the page.
Each open pull request can be acknowledged for 1, 7 or 30 days, for the whole team. It leaves the list until the time is up or its worst result changes. The list shows how many it hides, and the acknowledged view lists them with who acknowledged them and offers Unacknowledge. A fresh acknowledgement can be undone from the notice. The control is shown to every viewer and the API decides: a refusal is explained inline, with a Sign in button when signing in would help.
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info
📝 Walkthrough
Merge Risk: ⚪ Minimal · up to No merge-blocking issue is established for the acknowledgement changes. Normal validation can proceed. Pre-merge checks |
|
Require updatecli/udash#480
Description
Test
To test this pull request, you can run the following commands:
Additional Information
Tradeoff
Potential improvement
Summary by CodeRabbit