chore: Delete gitignore for server

[jennifer-shehane]

Additional details

Revert change made in https://github.com/cypress-io/cypress/pull/27848/files#diff-ac6c6375f4f1da4088831e74ffba8c895a2d5b8940d64aa4dbe345b0df9f19a3 that will ignore all JS files within the server package in git.

Steps to test

Tests pass

How has the user experience changed?

It shouldn't change. I have no idea if some changes were attempted to be made to these files that wasn't commited. We'll have to assume not.

PR Tasks

• Have tests been added/updated?
• Has a PR for user-facing changes been opened in cypress-documentation?
• Have API changes been updated in the type definitions?

[cypress]

9 flaky tests on run #54107 ↗︎

0

28947

1341

0

9

Details:

empty commit
Project: cypress	Commit: dae2bd9954
Status: Passed	Duration: 20:40 💡
Started: Feb 20, 2024 10:05 PM	Ended: Feb 20, 2024 10:26 PM

  commands/files.cy.js • 1 flaky test • 5x-driver-electron

View Output

Test		Artifacts
... > throws a specific error when file exists when it shouldn't		Test Replay

  project-setup.cy.ts • 1 flaky test • launchpad-e2e

View Output

Test		Artifacts
Launchpad: Setup Project > switch testing types > takes the user to first step of e2e setup when switching from app		Test Replay Screenshots

  config-warning.cy.ts • 1 flaky test • launchpad-e2e

View Output

Test		Artifacts
experimentalStudio > is a valid config for e2e testing		Test Replay Screenshots

  specs_list_latest_runs.cy.ts • 1 flaky test • app-e2e

View Output

Test		Artifacts
App/Cloud Integration - Latest runs and Average duration > when no runs are recorded > shows placeholders for all visible specs		Test Replay Screenshots

  commands/waiting.cy.js • 2 flaky tests • 5x-driver-chrome:beta

View Output

Test		Artifacts
... > errors > throws when route is never resolved		Test Replay
... > errors > throws when waiting for 2nd response to route		Test Replay

The first 5 flaky specs are shown, see all 6 specs in Cypress Cloud.

Review all test suite changes for PR #28977 ↗︎

[cypress-bot]

Released in 13.6.6.

This comment thread has been locked. If you are still experiencing this issue after upgrading to
Cypress v13.6.6, please open a new issue.