Running workflow with headless=false no longer opens headless chrome browser

[alexcampbell86]

Version: cypress-io/github-action@v2
Cypress version: 8.5

I'm running the workflow (latest version) with the parameter headless=false

But when the browser launches, it is actually in headless mode:

[juandavidkincaid]

+1

[sergiubcn]

Folks following this thread can maybe upvote my PR so we can get it merged sooner #409

[ricardo-dematos]

cypress-io/github-action@v5 no longer has option headless.

---

Setting browser: chrome and headed: true works as expected.

Run cypress-io/github-action@v5
  with:
    working-directory: e2e-tests
    env: host="***",username="***",password="***"
    browser: chrome
    headed: true
    record: false
    publish-summary: true
    component: false
(....)
  ┌────────────────────────────────────────────────────────────────────────────────────────────────┐
  │ Cypress:        12.17.1                                                                        │
  │ Browser:        Chrome 114                                                                     │
  │ Node Version:   v18.16.1 (/opt/hostedtoolcache/node/18.16.1/x64/bin/node)                      │
  │ Specs:          8 found (login/login-message.cy.ts, login/login.cy.ts, login/reset-password.cy │
  │                 .ts, specifications/create-specification.feature, specifications/delete-specif │
  │                 ication.feature, specifications/specifications.cy.ts, wizards/quick-start/quic │
  │                 k-start-wizard.cy.ts, ...)                                                     │
  │ Searched:       **/*.{cy.ts,feature}                                                           │
  │ Experiments:    experimentalMemoryManagement=true,experimentalWebKitSupport=true               │
  └────────────────────────────────────────────────────────────────────────────────────────────────┘

---

I suggest closing this issue.

---

Relates to:

• Impossible to activate headed mode  #403

[nagash77]

I am going to close this issue as it is quite old at this point. If folks are seeing this behavior in current versions of github-action please open a new ticket with a reproducible example and we will be happy to investigate.