fix: prevent crash when pullRequest is null in collaborators fetch

[devMonkRahul]

🐛 Fix: Cannot read properties of null (reading 'pullRequest') when loading collaborators

📌 Related Issue

Closes #1

---

📝 Summary

This PR fixes a runtime error that occurs when fetching collaborators. The application was attempting to access pullRequest on a null object, causing a crash and preventing the dashboard from loading properly.

---

🔍 Root Cause

The issue was caused by missing null/undefined checks before accessing the pullRequest property in the collaborators fetching logic.

---

✅ Fix Implemented

• Added proper null/undefined checks before accessing pullRequest
• Improved handling of API responses to avoid unexpected crashes
• Ensured the UI remains stable even when data is missing or delayed

---

🧪 Testing

• Reproduced the issue locally and verified the fix
• Ran the following commands successfully:

  npm run test
  npm run build
  
  
  

[vercel]

@devMonkRahul is attempting to deploy a commit to the wbfoss' projects Team on Vercel.

A member of the Team first needs to authorize it.