Results page banner priority update

[jzgom067]

To align better with our "4-step process", the results page banner priority was updated.

When there are no participants:

• If you are the event creator, you are now prompted to share the link with others first instead of adding your availability.
• If you are NOT the event creator, it just tells you to add your availability (this is the current behavior).

The event creator is shown the banner to add availability after someone else has submitted their availability.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: cc3147ca-36a0-4d7d-800c-b76c73b6a380

📥 Commits

Reviewing files that changed from the base of the PR and between 120036e and e6f184f.

📒 Files selected for processing (2)

• frontend/src/app/(event)/[event-code]/page-client.tsx
• frontend/src/features/event/results/components/banners.tsx

---

Walkthrough

The event results page now passes isCreator to getResultBanners. The banner generator accepts this parameter and reuses a shared “Waiting for responses…” share-link banner. Creator events with no participants use this banner. Participated events with one participant also use this banner.

Mergeability Score: ⚪ Minimal · up to e6f18

This localized banner-priority change introduces no actionable merge-blocking risk based on the available evidence and is merge-ready after normal checks and review.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}