Document GITHUB_TOKEN settings - Cypress Cloud recording #1273

Activity

1. MikeMcC399

   added

   documentationImprovements or additions to documentationImprovements or additions to documentation

   type: enhancementNew feature or requestNew feature or request

   Cypress Cloud

   on Oct 3, 2024
2. MikeMcC399

   self-assigned this

   on Oct 3, 2024
3. MikeMcC399 commented on Oct 4, 2024

   

   MikeMcC399

   on Oct 4, 2024

   Last edited by MikeMcC399

   CollaboratorAuthor

   More actions

   @tbiethman

   • Can you provide any assistance on this? It's a result of feat: [CYCLOUD-1447] Auto-detect PR numbers #1009 and I'm not sure that I understand the whole story yet, so I'm trying to reverse engineer it.
   • I don't know exactly what circumstances permissions are needed. In a test with all permissions disabled (permissions: {}) recording was successful. From reports of other users I know that this is not always the case.
4. MikeMcC399

   changed the title [-]Document `GITHUB_TOKEN` settings[/-] [+]Document `GITHUB_TOKEN` settings - Cypress Cloud recording[/+] on Oct 4, 2024
5. MikeMcC399

   removed their assignment

   on Oct 4, 2024
6. MikeMcC399 commented on Oct 21, 2024

   

   MikeMcC399

   on Oct 21, 2024

   CollaboratorAuthor

   More actions

   This is a topic for the Cypress Cloud team.
7. VolodymyrSmahliuk commented on Jan 16, 2025

   

   VolodymyrSmahliuk

   on Jan 16, 2025

   Last edited by VolodymyrSmahliuk

   More actions

   Additional permissions should be documented:

   permissions:
     contents: read # This is required for actions/checkout
     pull-requests: read # This is required for Cypress run
     actions: write # This is required for Cypress run

   I published the detailed fixes in (#1272 (comment)). I applied that on my system to run the Cypress Job on GitHub Actions. Please, consider it when writing the documentation.