[GH-ISSUE #2625] pulling remote actions with +x scripts fails with Permission denied on Windows #1194

New issue

Open

opened 2026-03-01 21:49:34 +03:00 by kerem · 12 comments

kerem commented 2026-03-01 21:49:34 +03:00

Owner

Copy link

Originally created by @oliverrahner on GitHub (Jan 20, 2025).
Original GitHub issue: https://github.com/nektos/act/issues/2625

Bug report info

act version:            0.2.71
GOOS:                   windows
GOARCH:                 amd64
NumCPU:                 24
Docker host:            DOCKER_HOST environment variable is not set
Sockets found:
        \\.\pipe\docker_engine(broken)
Config files:
        C:\Users\Oliver\AppData\Local\act\actrc:
                -P ubuntu-latest=catthehacker/ubuntu:act-latest
                -P ubuntu-22.04=catthehacker/ubuntu:act-22.04
                -P ubuntu-20.04=catthehacker/ubuntu:act-20.04
                -P ubuntu-18.04=catthehacker/ubuntu:act-18.04
Build info:
        Go version:            go1.23.4
        Module path:           github.com/nektos/act
        Main version:          (devel)
        Main path:             github.com/nektos/act
        Main checksum:
        Build settings:
                -buildmode:           exe
                -compiler:            gc
                -ldflags:             -s -w -X main.version=0.2.71 -X main.commit=0006dee285413b6f2a432f65a0947e5b1d8be2f7 -X main.date=2025-01-01T02:31:04Z -X main.builtBy=goreleaser
                CGO_ENABLED:          0
                GOARCH:               amd64
                GOOS:                 windows
                GOAMD64:              v1
                vcs:                  git
                vcs.revision:         0006dee285413b6f2a432f65a0947e5b1d8be2f7
                vcs.time:             2025-01-01T02:30:43Z
                vcs.modified:         false
Docker Engine:
        Engine version:        27.1.1
        Engine runtime:        runc
        Cgroup version:        1
        Cgroup driver:         cgroupfs
        Storage driver:        overlay2
        Registry URI:          https://index.docker.io/v1/
        OS:                    Docker Desktop
        OS type:               linux
        OS version:
        OS arch:               x86_64
        OS kernel:             5.15.167.4-microsoft-standard-WSL2
        OS CPU:                24
        OS memory:             31665 MB
        Security options:
                name=seccomp,profile=unconfined

Command used with act

act -v

Describe issue

My workflow uses the custom action rlespinasse/github-slug-action@v5.

When running the step, this happens:

[Build and Push Docker Image/build] [DEBUG] Writing entry to tarball workflow/2-composite-prefligth.sh len:34
[Build and Push Docker Image/build] [DEBUG] Extracting content to '/var/run/act'
[Build and Push Docker Image/build]   🐳  docker exec cmd=[bash --noprofile --norc -e -o pipefail /var/run/act/workflow/2-composite-prefligth.sh] user= workdir=
[Build and Push Docker Image/build] [DEBUG] Exec command '[bash --noprofile --norc -e -o pipefail /var/run/act/workflow/2-composite-prefligth.sh]'
[Build and Push Docker Image/build] [DEBUG] Working directory '/mnt/d/Coding/projectname'
| /var/run/act/workflow/2-composite-prefligth.sh: line 2: /var/run/act/actions/rlespinasse-github-slug-action@v5/preflight.sh: Permission denied
[Build and Push Docker Image/build]   ❌  Failure - Main $GITHUB_ACTION_PATH/preflight.sh
[Build and Push Docker Image/build] exitcode '126': failure

During troubleshooting, I recognized that, immediately after cloneing the action's repository, git diff from inside ~/.cache/act/rlespinasse-github-slug-action@v5 shows the following:

~/.cache/act/rlespinasse-github-slug-action@v5 $ git diff
diff --git a/preflight.sh b/preflight.sh
old mode 100755
new mode 100644

When following the trail, I found that this go-git issue describes what's going on, so it really seems to be an upstream issue.

The workflow below is the MRE, thus doesn't do anything useful.

Link to GitHub repository

private

Workflow content

name: Build and Push Docker Image

on:
  push:

jobs:
  build:
    runs-on: [ubuntu-latest]

    steps:
      - name: Checkout repository
        uses: actions/checkout@v4

      - name: Slugify Github Variables
        uses: rlespinasse/github-slug-action@v5

Relevant log output

# -v doesn't provide useful output

[Build and Push Docker Image/build] ⭐ Run Main $GITHUB_ACTION_PATH/preflight.sh
[Build and Push Docker Image/build]   🐳  docker exec cmd=[bash --noprofile --norc -e -o pipefail /var/run/act/workflow/1-composite-prefligth.sh] user= workdir=
| /var/run/act/workflow/1-composite-prefligth.sh: line 2: /var/run/act/actions/rlespinasse-github-slug-action@v5/preflight.sh: Permission denied
[Build and Push Docker Image/build]   ❌  Failure - Main $GITHUB_ACTION_PATH/preflight.sh
[Build and Push Docker Image/build] exitcode '126': failure
[Build and Push Docker Image/build]   ❌  Failure - Main Slugify Github Variables
[Build and Push Docker Image/build] exitcode '126': failure

Additional information

No response

Originally created by @oliverrahner on GitHub (Jan 20, 2025). Original GitHub issue: https://github.com/nektos/act/issues/2625 ### Bug report info ```plain text act version: 0.2.71 GOOS: windows GOARCH: amd64 NumCPU: 24 Docker host: DOCKER_HOST environment variable is not set Sockets found: \\.\pipe\docker_engine(broken) Config files: C:\Users\Oliver\AppData\Local\act\actrc: -P ubuntu-latest=catthehacker/ubuntu:act-latest -P ubuntu-22.04=catthehacker/ubuntu:act-22.04 -P ubuntu-20.04=catthehacker/ubuntu:act-20.04 -P ubuntu-18.04=catthehacker/ubuntu:act-18.04 Build info: Go version: go1.23.4 Module path: github.com/nektos/act Main version: (devel) Main path: github.com/nektos/act Main checksum: Build settings: -buildmode: exe -compiler: gc -ldflags: -s -w -X main.version=0.2.71 -X main.commit=0006dee285413b6f2a432f65a0947e5b1d8be2f7 -X main.date=2025-01-01T02:31:04Z -X main.builtBy=goreleaser CGO_ENABLED: 0 GOARCH: amd64 GOOS: windows GOAMD64: v1 vcs: git vcs.revision: 0006dee285413b6f2a432f65a0947e5b1d8be2f7 vcs.time: 2025-01-01T02:30:43Z vcs.modified: false Docker Engine: Engine version: 27.1.1 Engine runtime: runc Cgroup version: 1 Cgroup driver: cgroupfs Storage driver: overlay2 Registry URI: https://index.docker.io/v1/ OS: Docker Desktop OS type: linux OS version: OS arch: x86_64 OS kernel: 5.15.167.4-microsoft-standard-WSL2 OS CPU: 24 OS memory: 31665 MB Security options: name=seccomp,profile=unconfined ``` ### Command used with act ```sh act -v ``` ### Describe issue My workflow uses the custom action `rlespinasse/github-slug-action@v5`. When running the step, this happens: ``` [Build and Push Docker Image/build] [DEBUG] Writing entry to tarball workflow/2-composite-prefligth.sh len:34 [Build and Push Docker Image/build] [DEBUG] Extracting content to '/var/run/act' [Build and Push Docker Image/build] 🐳 docker exec cmd=[bash --noprofile --norc -e -o pipefail /var/run/act/workflow/2-composite-prefligth.sh] user= workdir= [Build and Push Docker Image/build] [DEBUG] Exec command '[bash --noprofile --norc -e -o pipefail /var/run/act/workflow/2-composite-prefligth.sh]' [Build and Push Docker Image/build] [DEBUG] Working directory '/mnt/d/Coding/projectname' | /var/run/act/workflow/2-composite-prefligth.sh: line 2: /var/run/act/actions/rlespinasse-github-slug-action@v5/preflight.sh: Permission denied [Build and Push Docker Image/build] ❌ Failure - Main $GITHUB_ACTION_PATH/preflight.sh [Build and Push Docker Image/build] exitcode '126': failure ``` During troubleshooting, I recognized that, immediately after `clone`ing the action's repository, `git diff` from inside `~/.cache/act/rlespinasse-github-slug-action@v5` shows the following: ``` ~/.cache/act/rlespinasse-github-slug-action@v5 $ git diff diff --git a/preflight.sh b/preflight.sh old mode 100755 new mode 100644 ``` When following the trail, I found that [this go-git issue](https://github.com/go-git/go-git/issues/771) describes what's going on, so it really seems to be an upstream issue. The workflow below is the MRE, thus doesn't do anything useful. ### Link to GitHub repository private ### Workflow content ```yml name: Build and Push Docker Image on: push: jobs: build: runs-on: [ubuntu-latest] steps: - name: Checkout repository uses: actions/checkout@v4 - name: Slugify Github Variables uses: rlespinasse/github-slug-action@v5 ``` ### Relevant log output ```sh # -v doesn't provide useful output [Build and Push Docker Image/build] ⭐ Run Main $GITHUB_ACTION_PATH/preflight.sh [Build and Push Docker Image/build] 🐳 docker exec cmd=[bash --noprofile --norc -e -o pipefail /var/run/act/workflow/1-composite-prefligth.sh] user= workdir= | /var/run/act/workflow/1-composite-prefligth.sh: line 2: /var/run/act/actions/rlespinasse-github-slug-action@v5/preflight.sh: Permission denied [Build and Push Docker Image/build] ❌ Failure - Main $GITHUB_ACTION_PATH/preflight.sh [Build and Push Docker Image/build] exitcode '126': failure [Build and Push Docker Image/build] ❌ Failure - Main Slugify Github Variables [Build and Push Docker Image/build] exitcode '126': failure ``` ### Additional information _No response_

kerem added the

kind/bug

label 2026-03-01 21:49:34 +03:00

kerem commented 2026-03-01 21:49:35 +03:00

Author

Owner

Copy link

@Redrox477 commented on GitHub (Feb 19, 2025):

Now experiencing the same error , using reviewdog/action-eslint@v1 getting
[reviewdog/runner / eslint] [DEBUG] Working directory '/mnt/c/Projects/Github_test/Git_Actions_test' | /var/run/act/workflow/3-composite-0.sh: line 2: /var/run/act/actions/reviewdog-action-eslint@v1/script.sh: Permission denied [reviewdog/runner / eslint] ❌ Failure - Main $GITHUB_ACTION_PATH/script.sh [reviewdog/runner / eslint] exitcode '126': failure

<!-- gh-comment-id:2669362092 --> @Redrox477 commented on GitHub (Feb 19, 2025): Now experiencing the same error , using reviewdog/action-eslint@v1 getting `[reviewdog/runner / eslint] [DEBUG] Working directory '/mnt/c/Projects/Github_test/Git_Actions_test' | /var/run/act/workflow/3-composite-0.sh: line 2: /var/run/act/actions/reviewdog-action-eslint@v1/script.sh: Permission denied [reviewdog/runner / eslint] ❌ Failure - Main $GITHUB_ACTION_PATH/script.sh [reviewdog/runner / eslint] exitcode '126': failure`

kerem commented 2026-03-01 21:49:35 +03:00

Author

Owner

Copy link

@mitkonikov commented on GitHub (Feb 20, 2025):

I'm getting the same error, when using xu-cheng-texlive-action@v2, getting:

[Build LaTeX book/build_latex]   🐳  docker exec cmd=[bash --noprofile --norc -e -o pipefail /var/run/act/workflow/1-composite-0.sh] user= workdir=
| /var/run/act/workflow/1-composite-0.sh: line 2: /var/run/act/actions/xu-cheng-texlive-action@v2/action.sh: Permission denied
[Build LaTeX book/build_latex]   ❌  Failure - Main "${GITHUB_ACTION_PATH}/action.sh"
[Build LaTeX book/build_latex] exitcode '126': failure
[Build LaTeX book/build_latex]   ❌  Failure - Main xu-cheng/texlive-action@v2
[Build LaTeX book/build_latex] exitcode '126': failure

<!-- gh-comment-id:2672042990 --> @mitkonikov commented on GitHub (Feb 20, 2025): I'm getting the same error, when using `xu-cheng-texlive-action@v2`, getting: ``` [Build LaTeX book/build_latex] 🐳 docker exec cmd=[bash --noprofile --norc -e -o pipefail /var/run/act/workflow/1-composite-0.sh] user= workdir= | /var/run/act/workflow/1-composite-0.sh: line 2: /var/run/act/actions/xu-cheng-texlive-action@v2/action.sh: Permission denied [Build LaTeX book/build_latex] ❌ Failure - Main "${GITHUB_ACTION_PATH}/action.sh" [Build LaTeX book/build_latex] exitcode '126': failure [Build LaTeX book/build_latex] ❌ Failure - Main xu-cheng/texlive-action@v2 [Build LaTeX book/build_latex] exitcode '126': failure ```

kerem commented 2026-03-01 21:49:35 +03:00

Author

Owner

Copy link

@drakonkat commented on GitHub (Feb 24, 2025):

Same issue here

<!-- gh-comment-id:2678011373 --> @drakonkat commented on GitHub (Feb 24, 2025): Same issue here

kerem commented 2026-03-01 21:49:35 +03:00

Author

Owner

Copy link

@Redrox477 commented on GitHub (Feb 24, 2025):

So, I inspected the files while the docker container is built when running act cmd, the script.sh file did not have a execute permission -rw-rw-rw-. I manually set the permission using chmod +x but when running act cmd again, the container is rebuilt and permission to execute file is revoked to just read, write

<!-- gh-comment-id:2678038310 --> @Redrox477 commented on GitHub (Feb 24, 2025): So, I inspected the files while the docker container is built when running act cmd, the script.sh file did not have a execute permission -rw-rw-rw-. I manually set the permission using chmod +x <path-to-file> but when running act cmd again, the container is rebuilt and permission to execute file is revoked to just read, write 

kerem commented 2026-03-01 21:49:36 +03:00

Author

Owner

Copy link

@mitkonikov commented on GitHub (Feb 24, 2025):

One way I found that I could temporarily fix the issue is to modify the action repo when executing the script to execute it with bash script.sh. But this requires manually cloning the action repo locally, updating it and changing the yml path to the local action repo instead (but this complicates the job and is only a temporary solution, since there's no way to flip between local and remote action repos).

<!-- gh-comment-id:2678176799 --> @mitkonikov commented on GitHub (Feb 24, 2025): One way I found that I could temporarily fix the issue is to modify the action repo when executing the script to execute it with `bash script.sh`. But this requires manually cloning the action repo locally, updating it and changing the `yml` path to the local action repo instead (but this complicates the job and is only a temporary solution, since there's no way to flip between local and remote action repos).

kerem commented 2026-03-01 21:49:36 +03:00

Author

Owner

Copy link

@ChristopherHX commented on GitHub (Feb 24, 2025):

iff you are not using docker actions, you could enable --use-new-action-cache to have the +x bit preserved.

Yes the workdir on windows, has not the ability to preserve the executable bit

<!-- gh-comment-id:2678355432 --> @ChristopherHX commented on GitHub (Feb 24, 2025): iff you are not using docker actions, you could enable `--use-new-action-cache` to have the `+x` bit preserved. Yes the workdir on windows, has not the ability to preserve the executable bit

kerem commented 2026-03-01 21:49:36 +03:00

Author

Owner

Copy link

@oliverrahner commented on GitHub (Feb 24, 2025):

Yes the workdir on windows, has not the ability to preserve the executable bit

This is not an inherent issue with Git on Windows! When running git clone manually, followed by git diff, there is no difference, as opposed to the thing we see here.

Refer to the upstream issue I linked above for detials

<!-- gh-comment-id:2679468930 --> @oliverrahner commented on GitHub (Feb 24, 2025): > Yes the workdir on windows, has not the ability to preserve the executable bit This is _not_ an inherent issue with Git on Windows! When running git clone manually, followed by git diff, there is no difference, as opposed to the thing we see here. Refer to the upstream issue I linked above for detials

kerem commented 2026-03-01 21:49:36 +03:00

Author

Owner

Copy link

@ChristopherHX commented on GitHub (Feb 24, 2025):

I want to provide you some insights, this issue is not related to any bug of go-git or git for windows

Just make the step act does yourself on windows

• git clone with go-git or not
• git checkout
• tar folder of checkout without using git / go-git api
• tar has no +x bit, on windows systems.
  How would the tar command know if the file has been executable? It can only do this on unix like systems / by using extended undocumented ntfs metadata (wsl1 has a way)

What I have done outside of act was, ask git for windows for the unix mask and merge it with the data of your disk. I no longer remember what I did in act for the workdir.

This is a design issue of the action-cache

Now using cli feature toggle --use-new-action-cache the whole thing changes

• git init
• git fetch
• go-git worktree is now tared in memory
  • no filesystem involved, no OS specific differences
  • unix permission mask copied out of the git
  • no checkout
  • +x is available after unpacking in the linux filesyste

When running git clone manually, followed by git diff, there is no difference, as opposed to the thing we see here.

As far I know, git ignores the +x bit between git worktree and filesystem on windows. You never want to commit a executable bit removal from windows without using git commands.

<!-- gh-comment-id:2679545759 --> @ChristopherHX commented on GitHub (Feb 24, 2025): I want to provide you some insights, this issue is not related to any bug of go-git or git for windows Just make the step act does yourself on windows - git clone with go-git or not - git checkout - tar folder of checkout without using git / go-git api - **tar has no `+x` bit**, on windows systems. How would the tar command know if the file has been executable? It can only do this on unix like systems / by using extended undocumented ntfs metadata (wsl1 has a way) What I have done outside of act was, ask git for windows for the unix mask and merge it with the data of your disk. I no longer remember what I did in act for the workdir. This is a design issue of the action-cache Now using cli feature toggle `--use-new-action-cache` the whole thing changes - git init - git fetch - go-git worktree is now tared in memory - no filesystem involved, no OS specific differences - unix permission mask copied out of the git - no checkout - +x is available after unpacking in the linux filesyste > When running git clone manually, followed by git diff, there is no difference, as opposed to the thing we see here. As far I know, git ignores the `+x` bit between git worktree and filesystem on windows. You never want to commit a executable bit removal from windows without using git commands.

kerem commented 2026-03-01 21:49:36 +03:00

Author

Owner

Copy link

@mitkonikov commented on GitHub (Feb 24, 2025):

Is there a way to inject a custom command when executing a docker cmd script? Is there a planned resolution for the issue?

<!-- gh-comment-id:2679640575 --> @mitkonikov commented on GitHub (Feb 24, 2025): Is there a way to inject a custom command when executing a docker cmd script? Is there a planned resolution for the issue?

kerem commented 2026-03-01 21:49:36 +03:00

Author

Owner

Copy link

@ChristopherHX commented on GitHub (Feb 24, 2025):

Is there a way to inject a custom command when executing a docker cmd script?

No, you need to add it to your yaml and add an if: env.ACT to skip it outside of act.

Is there a planned resolution for the issue?

I had a plan last year between 30. October 2024 - 20. December (yes this predates this issue) see https://github.com/nektos/act/pull/2509.
But due to lack of public code reviews over a period of 2 Months, I stopped this plan and we still have this problem. Similar reason why I didn't comment of this repost of a well known defect earlier.

EDIT fixed year to 2024

<!-- gh-comment-id:2679775600 --> @ChristopherHX commented on GitHub (Feb 24, 2025): > Is there a way to inject a custom command when executing a docker cmd script? No, you need to add it to your yaml and add an `if: env.ACT` to skip it outside of act. > Is there a planned resolution for the issue? I had a plan last year between 30. October 2024 - 20. December (yes this predates this issue) see <https://github.com/nektos/act/pull/2509>. But due to lack of public code reviews over a period of 2 Months, I stopped this plan and we still have this problem. Similar reason why I didn't comment of this repost of a well known defect earlier. **EDIT fixed year to 2024**

kerem commented 2026-03-01 21:49:36 +03:00

Author

Owner

Copy link

@mitkonikov commented on GitHub (Feb 24, 2025):

If you need help in code reviews or testing features, you can sure tag me. Sometimes, I want to relax reading code and issues. 😉

<!-- gh-comment-id:2679792503 --> @mitkonikov commented on GitHub (Feb 24, 2025): If you need help in code reviews or testing features, you can sure tag me. Sometimes, I want to relax reading code and issues. 😉

kerem commented 2026-03-01 21:49:36 +03:00

Author

Owner

Copy link

@ChristopherHX commented on GitHub (Feb 25, 2025):

Update starting with upcoming act v0.2.75

Just add --use-new-action-cache as a line in your .actrc file, the fix for the docker actions has been merged and known issues are resolved.

<!-- gh-comment-id:2681887870 --> @ChristopherHX commented on GitHub (Feb 25, 2025): Update starting with upcoming act `v0.2.75` Just add `--use-new-action-cache` as a line in your `.actrc` file, the fix for the docker actions has been merged and known issues are resolved.

Sign in to join this conversation.

No Branch/Tag specified

Branches Tags

master

dependabot/go_modules/github.com/go-git/go-git/v5-5.18.0

dependabot/go_modules/dependencies-08815e2262

mergify/configuration-deprecated-update

dependabot/github_actions/dependencies-a3a104477f

chore/simplify-ci-and-makefile

dependabot/go_modules/golang.org/x/crypto-0.45.0

dependabot/go_modules/github.com/go-viper/mapstructure/v2-2.4.0

panekj/ci/improve-jobs

fix-skip-non-yaml-files-in-dir

normalize-pull-rebuild-flags

fix-no-recurse-by-default

2517-poor-error-for-incomplete-action-step

2472-make-use-new-action-cache-the-new-default-for-downloading-actions

act-tart

act-lxc

act-oidc

act-dind

avoid-slash-in-actor

dependabot/go_modules/github.com/docker/docker-26.1.4incompatible

meta-keep-filetime

local-repository-action-cache

pr-merger

update-docker-deps

follow_local_action_symlink

boltdb-lock-in-handler

use-socket-path

no-pull-no-rebuild

path-issues

fix/env

feat/podman

refactor/testdata

v0.2.87

v0.2.86

v0.2.85

v0.2.84

v0.2.83

v0.2.82

v0.2.81

v0.2.80

v0.2.79

v0.2.78

v0.2.77

v0.2.76

v0.2.75

v0.2.74

v0.2.73

v0.2.72

v0.2.71

v0.2.70

v0.2.69

v0.2.68

v0.2.67

v0.2.66

v0.2.65

v0.2.64

v0.2.63

v0.2.62

v0.2.61

v0.2.60

v0.2.59

v0.2.58

v0.2.57

v0.2.56

v0.2.55

v0.2.54

v0.2.53

v0.2.52

v0.2.51

v0.2.50

v0.2.49

v0.2.48

v0.2.47

v0.2.46

v0.2.45

v0.2.44

v0.2.43

v0.2.42

v0.2.41

v0.2.40

v0.2.39

v0.2.38

v0.2.37

v0.2.36

v0.2.35

v0.2.34

v0.2.33

v0.2.32

v0.2.31

v0.2.30

v0.2.29

v0.2.28

v0.2.27

v0.2.26

v0.2.25

v0.2.24

v0.2.23

v0.2.22

v0.2.21

v0.2.20

v0.2.19

v0.2.18

v0.2.17

v0.2.16

v0.2.15

v0.2.14

v0.2.13

v0.2.12

v0.2.11

v0.2.10

v0.2.9

v0.2.8

v0.2.7

v0.2.6

v0.2.5

v0.2.4

v0.2.3

v0.2.2

v0.2.1

v0.2.0

v0.1.3

v0.1.2

v0.1.1

v0.1.0

v0.0.5

v0.0.4

v0.0.3

v0.0.2

v0.0.1

Labels

Clear labels   

area/action

  

area/cli

  

area/docs

  

area/image

  

area/runner

  

area/workflow

  

backlog

  

confirmed/not-planned

  

kind/bug

  

kind/discussion

  

kind/external

  

kind/feature-request

  

kind/question

  

meta/duplicate

  

meta/invalid

  

meta/need-more-info

  

meta/resolved

  

meta/wontfix

  

meta/workaround

  

needs-work

  

pull-request

Mirrored from GitHub Pull Request

  

review/not-planned

  

size/M

  

size/XL

  

size/XXL

  

stale

  

stale-exempt

No labels

area/action

area/cli

area/docs

area/image

area/runner

area/workflow

backlog

confirmed/not-planned

kind/bug

kind/discussion

kind/external

kind/feature-request

kind/question

meta/duplicate

meta/invalid

meta/need-more-info

meta/resolved

meta/wontfix

meta/workaround

needs-work

pull-request

review/not-planned

size/M

size/XL

size/XXL

stale

stale-exempt

Milestone

Clear milestone

No items

No milestone

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

1 participant

Notifications

Subscribe

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/act#1194

No description provided.