Distinguish empty-state messages in PullRequestsTab (no repos vs no PRs vs no filter matches)

[Jagadeeshftw]

📌 Description

src/features/maintainers/components/pull-requests/PullRequestsTab.tsx renders a single generic empty message that conflates three distinct conditions: no repositories selected, repositories selected but containing no PRs, and active filters returning no matches. Users cannot tell why the list is empty or how to recover.

💡 Why it matters: A precise empty state tells the user the next action (select a repo, clear filters), reducing confusion.

🧩 Requirements and context

• Detect and branch the three states explicitly.
• "No repos selected" prompts repository selection.
• "No PRs" reflects an empty result for selected repos.
• "No matches" appears when filters exclude all rows and offers a Clear Filters action.
• Ensure the empty state is announced (role="status").

Non-functional requirements

• Must be secure, tested, and documented.
• Should be efficient and easy to review.

🛠️ Suggested execution

1. Fork the repo and create a branch

git checkout -b feat/pr-tab-empty-states

2. Implement changes

• Write/modify the relevant source: src/features/maintainers/components/pull-requests/PullRequestsTab.tsx
• Write comprehensive tests: src/features/maintainers/components/pull-requests/PullRequestsTab.test.tsx
• Add documentation: inline TSDoc on the empty-state logic
• Include TSDoc comments
• Validate security assumptions: n/a

3. Test and commit

• Run tests:

npm run test

• Cover edge cases: each of the three conditions, plus transition from filtered-empty back to results
• Include test output and security notes in the PR description.

Example commit message

feat(maintainers): differentiate PR list empty states

✅ Acceptance criteria

• Three distinct empty-state messages render correctly
• "No matches" offers Clear Filters
• Empty state announced via role="status"
• Tests cover all three conditions

🔒 Security notes

None; presentation only.

📋 Guidelines

• Minimum 95% test coverage
• Clear documentation
• Timeframe: 96 hours

[Menjay7]

Hi! I came across this issue and would love to work on it. I have experience with similar tasks and I'm confident I can investigate, implement a clean solution, and thoroughly test it before submitting a PR. If the issue is still open, I would appreciate it if you could assign it to me. Thank you!

[ObaHacker]

Good morning, Chief Maintainer,

I am an experienced software developer with a background in open-source contributions. I would like to work on this issue and contribute a clean, well-structured, and maintainable solution.

If possible, I would appreciate the opportunity to take it on. I’m ready to follow any contribution guidelines and provide timely updates.

Thank you for your consideration.

[mrnetwork0001]

Hi, I would love to work on this issue and request to have it assigned to me.

I am confident in resolving this cleanly by updating PullRequestsTab.tsx to handle the three distinct empty states explicitly and adding role="status" for proper accessibility.

I will also write comprehensive tests in PullRequestsTab.test.tsx to cover all three conditions and verify that the interface transitions correctly between empty and populated states.

[grantfox-oss]

🦊 GrantFox — @ObaHacker has been assigned to this issue as part of the Official Campaign campaign!

Next steps:

1. Open a Pull Request referencing this issue (e.g., Closes #81)
2. Your PR will be reviewed by the Grainlify maintainers

Good luck! Track your progress on GrantFox.

[grantfox-oss]

🎉 This issue has been marked as completed on GrantFox as part of the Official Campaign campaign!

@ObaHacker's PR #212 was approved and merged by @Jagadeeshftw.

🏆 @ObaHacker: You earned 35 FoxPoints for this contribution! Your current tier: Explorer (86 total points). Track your full progress on GrantFox.

👏 Great work, @ObaHacker! Keep contributing to Grainlify.