Skip to content

[CLEAN] Synthetic Benchmark PR #26833 - fix: hide team members details when hideOrganizerEmail is enabled#543

Open
ofir-frd wants to merge 1 commit intobase_pr_26833_20260120_2871from
clean_pr_26833_20260120_2871
Open

[CLEAN] Synthetic Benchmark PR #26833 - fix: hide team members details when hideOrganizerEmail is enabled#543
ofir-frd wants to merge 1 commit intobase_pr_26833_20260120_2871from
clean_pr_26833_20260120_2871

Conversation

@ofir-frd
Copy link
Copy Markdown

Benchmark PR calcom#26833

Type: Clean (correct implementation)

Original PR Title: fix: hide team members details when hideOrganizerEmail is enabled
Original PR Description: ## What does this PR do?

Hide organizer and team member emails when an event type has hideOrganizerEmail enabled. Applies consistently across booking UI, confirmation view, emails, and generated “Who” text.

  • Bug Fixes
    • Booking list and details: hide host/team emails and email actions when hidden.
    • Booking success view: hide email for hosts/team members (incl. round-robin) while still showing attendee phones; ignores SMS proxy emails as before.
    • Emails: omit organizer and team member emails in WhoInfo.
    • CalEventParser: remove team member email lines from “Who” output when hidden.

Written for commit c846e4a. Summary will update on new commits.

Original PR URL: calcom#26833

@github-actions
Copy link
Copy Markdown

Hey there and thank you for opening this pull request! 👋🏼

We require pull request titles to follow the Conventional Commits specification and it looks like your proposed title needs to be adjusted.

Details:

No release type found in pull request title "[CLEAN] Synthetic Benchmark PR #26833 - fix: hide team members details when hideOrganizerEmail is enabled". Add a prefix to indicate what kind of release this pull request corresponds to. For reference, see https://www.conventionalcommits.org/

Available types:
 - feat: A new feature
 - fix: A bug fix
 - docs: Documentation only changes
 - style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
 - refactor: A code change that neither fixes a bug nor adds a feature
 - perf: A code change that improves performance
 - test: Adding missing tests or correcting existing tests
 - build: Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm)
 - ci: Changes to our CI configuration files and scripts (example scopes: Travis, Circle, BrowserStack, SauceLabs)
 - chore: Other changes that don't modify src or test files
 - revert: Reverts a previous commit

@github-actions
Copy link
Copy Markdown

This PR has been marked as stale due to inactivity. If you're still working on it or need any help, please let us know or update the PR to keep it active.

@github-actions github-actions bot added the Stale label Mar 19, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant