Testing PR action change for .md file

[keithwillcode]

trafficstars

What does this PR do?

Fixes # (issue)

Environment: Staging(main branch) / Production

Type of change

• Bug fix (non-breaking change which fixes an issue)
• Chore (refactoring code, technical debt, workflow improvements)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

How should this be tested?

• [ ] Test A
• [ ] Test B

Checklist

• I haven't read the contributing guide
• My code doesn't follow the style guidelines of this project
• I haven't performed a self-review of my own code and corrected any misspellings
• I haven't commented my code, particularly in hard-to-understand areas
• I haven't checked if my PR needs changes to the documentation
• I haven't checked if my changes generate no new warnings
• I haven't added tests that prove my fix is effective or that my feature works
• I haven't checked if new and existing unit tests pass locally with my changes

[vercel[bot]]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
cal	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	May 17, 2023 5:38pm

1 Ignored Deployment

Name	Status	Preview	Comments	Updated (UTC)
ui	⬜️ Ignored (Inspect)			May 17, 2023 5:38pm

[github-actions[bot]]

📦 Next.js Bundle Analysis for @calcom/web

This analysis was generated by the Next.js Bundle Analysis action. 🤖

This PR introduced no changes to the JavaScript bundle! 🙌

[deploysentinel[bot]]

Current Playwright Test Results Summary

✅ 107 Passing - ❌ 1 Failing - ⚠️ 3 Flaky

Run may still be in progress, this comment will be updated as current testing workflow or job completes...

(Last updated on 05/30/2023 08:00:27pm UTC)

Run Details

Running Workflow PR Update on Github Actions

Commit: 963c107ee9a023d9de89651c69964bc0623863e0

Started: 05/30/2023 07:46:20pm UTC

❌ Failures

📄   apps/web/playwright/login.e2e.ts • 1 Failure

Test Case Results

Test Case	Last 7 days Failures	Last 7 days Flakes
user can login & logout succesfully login flow user & logout using dashboard Retry 2 • Retry 1 • Initial Attempt Error: page.waitForURL: Timeout 15000ms exceeded.... page.waitForURL: Timeout 15000ms exceeded. =========================== logs =========================== waiting for navigation to "/auth/logout" until "load" navigated to "http://127.0.0.1:3000/auth/logout" navigated to "http://127.0.0.1:3000/auth/logout" ============================================================	22.58% (98) 98 / 434 runs failed over last 7 days	1.84% (8) 8 / 434 runs flaked over last 7 days

---

⚠️ Flakes

📄   apps/web/playwright/event-types.e2e.ts • 1 Flake

Test Case Results

Test Case	Last 7 days Failures	Last 7 days Flakes
Event Types tests user -- new-booker can duplicate an existing event type Retry 1 • Initial Attempt	0.46% (2) 2 / 434 runs failed over last 7 days	0.92% (4) 4 / 434 runs flaked over last 7 days

---

📄   apps/web/playwright/booking-seats.e2e.ts • 2 Flakes

Top 1 Common Error Messages

null	2 Test Cases Affected

Test Case Results

Test Case	Last 7 days Failures	Last 7 days Flakes
Booking with Seats -- new-booker Reschedule for booking with seats -- old-booker Should reschedule booking with seats and if everyone rescheduled it should be deleted Retry 1 • Initial Attempt	0% (0) 0 / 326 runs failed over last 7 days	85.89% (280) 280 / 326 runs flaked over last 7 days
Booking with Seats -- old-booker Reschedule for booking with seats -- new-booker Should reschedule booking with seats and if everyone rescheduled it should be deleted Retry 1 • Initial Attempt	0.31% (1) 1 / 325 run failed over last 7 days	24% (78) 78 / 325 runs flaked over last 7 days

---

View Detailed Build Results

---