#!/bin/bash
set -euo pipefail

repo="geturbackend/urBackend"
pr_number="374"

gh api "repos/$repo/pulls/$pr_number/comments?per_page=100" \
  --paginate \
  --jq '.[] | select(.user.login == "coderabbitai[bot]" or .user.login == "coderabbitai") | {id, html_url, path, line, body}'

#!/bin/bash
set -euo pipefail

repo="geturbackend/urBackend"
requester="yash-pouranik"

issue_body=$(cat <<'EOF'
## Summary

Consolidate the duplicated configuration audit-log request logic in `apps/web-dashboard/src/pages/ConfigHistory.jsx`.

## Rationale

`fetchLogs` displays an error toast when a request fails. The separate initial-load and category-change logic only sets the page error state. This produces different failure behavior for equivalent audit-log requests.

## Required changes

- Remove the duplicated request implementation in the `useEffect` initial-load/category-change path.
- Use the shared `fetchLogs(1, category)` path for initial load and category changes.
- Keep loading state, error state, and error toast behavior consistent for initial load, category changes, refresh, retry, and pagination.
- Update React hook dependencies as needed.

## Affected area

- `apps/web-dashboard/src/pages/ConfigHistory.jsx`

## Acceptance criteria

- The page has one implementation for fetching configuration audit logs.
- A failed initial load displays the same error toast behavior as refresh, retry, and pagination failures.
- A failed category change displays the same error toast behavior as refresh, retry, and pagination failures.
- Existing loading, empty, retry, and pagination behavior remains intact.

## References

- Deferred from PR `#374`: https://github.com/geturbackend/urBackend/pull/374
- Code review comment: https://github.com/geturbackend/urBackend/pull/374#discussion_r3690248783
- Requested by: `@yash-pouranik`
EOF
)

gh issue create \
  --repo "$repo" \
  --title "Refactor ConfigHistory audit-log loading to use shared fetch logic" \
  --body "$issue_body" \
  --assignee "$requester"