Same cache folder prevents running the action on same VM using different runners

[VOVELEE]

Description:

Currently cache state directory is being hardcoded to the same 56acbeaa-1fef-4c79-8f84-7565e560fb03 value.
This causes permission issues in the following situation:

• One virtual machine has multiple GitHub runners
• Every runner is running under different user context
• Stale action is executed on multiple runners against multiple repositories

This causes state.txt to be owned by the user context of the first runner which executes the Github action preventing others runners to be able to use the state cache functionality.
One potential solution is to the STALE_DIR folder name to be a hash of the repository name. This will ensure that every repository will get its own state.

• Example error

Error: Error: EACCES: permission denied, open '/tmp/56acbeaa-1fef-4c79-8f84-7565e560fb03/state.txt'
Error: EACCES: permission denied, open '/tmp/56acbeaa-1fef-4c79-8f84-7565e560fb03/state.txt'

• Source code:

  stale/src/classes/state/state-cache-storage.ts

  Line 12 in f04443d

  const STALE_DIR = '56acbeaa-1fef-4c79-8f84-7565e560fb03';

Action version:

• Available in the latest one

Platform:

• Ubuntu
• macOS
• Windows

Runner type:

• Hosted
• Self-hosted

Repro steps:
See description.

Expected behavior:
See description.

Actual behavior:
See description.

[HarithaVattikuti]

Hello @VOVELEE 👋,
Thank you for reporting this issue. We will investigate it and get back to you as soon as we have some feedback.