starred/act
1
0
Fork 0
mirror of https://github.com/nektos/act.git synced 2026-04-26 09:25:54 +03:00
Code Issues 289 Projects Releases 5 Packages Wiki Activity

[GH-ISSUE #1795] act requries all yaml files in subdirectories to be workflows, but shouldn't #874

New issue
Closed
opened 2026-03-01 21:47:05 +03:00 by kerem · 6 comments
kerem commented 2026-03-01 21:47:05 +03:00
Owner
Copy link

Originally created by @sebix on GitHub (May 10, 2023).
Original GitHub issue: https://github.com/nektos/act/issues/1795

Bug report info

act version:            0.2.45
GOOS:                   linux
GOARCH:                 amd64
NumCPU:                 8
Docker host:            DOCKER_HOST environment variable is not set
Sockets found:
	/var/run/docker.sock
Config files:           
	/home/sebastianw/.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.18.10
	Module path:           github.com/nektos/act
	Main version:          (devel)
	Main path:             github.com/nektos/act
	Main checksum:         
	Build settings:
		-compiler:            gc
		-ldflags:             -s -w -X main.version=0.2.45 -X main.commit=f1df2ca5d6b315935cf9bb0d2a989175adf4e894 -X main.date=2023-05-01T02:18:49Z -X main.builtBy=goreleaser
		CGO_ENABLED:          0
		GOARCH:               amd64
		GOOS:                 linux
		GOAMD64:              v1
		vcs:                  git
		vcs.revision:         f1df2ca5d6b315935cf9bb0d2a989175adf4e894
		vcs.time:             2023-05-01T02:18:34Z
		vcs.modified:         false
Docker Engine:
	Engine version:        23.0.5-ce
	Engine runtime:        runc
	Cgroup version:        2
	Cgroup driver:         systemd
	Storage driver:        btrfs
	Registry URI:          https://index.docker.io/v1/
	OS:                    openSUSE Tumbleweed
	OS type:               linux
	OS version:            20230508
	OS arch:               x86_64
	OS kernel:             6.3.1-1-default
	OS CPU:                8
	OS memory:             31880 MB
	Security options:
		name=apparmor
		name=seccomp,profile=builtin
		name=cgroupns

Command used with act

act -l

Describe issue

This is the actual output:

Error: workflow is not valid. 'ansible-playbook.yml': yaml: unmarshal errors:
  line 5: cannot unmarshal !!seq into model.Workflow

But I expect that workflows are listed like

Stage  Job ID              Job name                                                Workflow name                        Workflow file        Events                    
0      ansible             Run ansible tests                                       Run ansible tests                    ansible-tests.yml    push,pull_request         
...

The issue is the file .github/workflows/scripts/ansible-playbook.yml which is not a workflow file, but act tries to parse it as a workflow file although it isn't placed in the workflow directory.

These workflows work on GitHub, see: https://github.com/certtools/intelmq/actions/

Link to GitHub repository

github.com/certtools/intelmq/

Workflow content

#Github Workflow to run ansible tests
#
#SPDX-FileCopyrightText: 2021 Birger Schacht <schacht@cert.at>
#SPDX-License-Identifier: AGPL-3.0-or-later
#
name: "Run ansible tests"
on:
  push:
    branches: [develop, maintenance, master]
    paths-ignore:
      - '.github/**'
  pull_request:
    branches: [develop, maintenance]
    paths-ignore:
      - '.github/**'

jobs:
  ansible:
    # temporary fix for https://github.com/actions/virtual-environments/issues/3080
    runs-on: ubuntu-22.04
    name: Run ansible tests

    steps:
    - name: Checkout repository
      uses: actions/checkout@v2
      with:
        path: ./src/intelmq

    - name: Checkout ansible scripts
      uses: actions/checkout@v2
      with:
        repository: certtools/intelmq-vagrant
        path: ./src/intelmq-vagrant
    - run: apt update && apt install -y podman
    - name: Run ansible tests
      run: podman run -e CI=${CI} -v ${GITHUB_WORKSPACE}/src:/src docker.io/debian:buster-slim /src/intelmq/.github/workflows/scripts/ansible.sh

Relevant log output

DEBU[0000] Loading environment from /home/user/dev/intelmq/.env 
DEBU[0000] Loading action inputs from /home/user/dev/intelmq/.input 
DEBU[0000] Loading secrets from /home/user/dev/intelmq/.secrets 
DEBU[0000] Evaluated matrix inclusions: map[]           
DEBU[0000] Loading workflows from '/home/user/dev/intelmq/.github/workflows' 
DEBU[0000] Loading workflows recursively                
DEBU[0000] Found workflow 'ansible-tests.yml' in '/home/user/dev/intelmq/.github/workflows/ansible-tests.yml' 
DEBU[0000] Found workflow 'build-docs.yml' in '/home/user/dev/intelmq/.github/workflows/build-docs.yml' 
DEBU[0000] Found workflow 'codeql-analysis.yml' in '/home/user/dev/intelmq/.github/workflows/codeql-analysis.yml' 
DEBU[0000] Found workflow 'codespell.excludelines' in '/home/user/dev/intelmq/.github/workflows/codespell.excludelines' 
DEBU[0000] Found workflow 'codespell.yml' in '/home/user/dev/intelmq/.github/workflows/codespell.yml' 
DEBU[0000] Found workflow 'debian-package.yml' in '/home/user/dev/intelmq/.github/workflows/debian-package.yml' 
DEBU[0000] Found workflow 'docker.yml' in '/home/user/dev/intelmq/.github/workflows/docker.yml' 
DEBU[0000] Found workflow 'pycodestyle.yml' in '/home/user/dev/intelmq/.github/workflows/pycodestyle.yml' 
DEBU[0000] Found workflow 'github.py' in '/home/user/dev/intelmq/.github/workflows/python/github.py' 
DEBU[0000] Found workflow 'pycodestyle_comment.py' in '/home/user/dev/intelmq/.github/workflows/python/pycodestyle_comment.py' 
DEBU[0000] Found workflow 'regexploit.yml' in '/home/user/dev/intelmq/.github/workflows/regexploit.yml' 
DEBU[0000] Found workflow 'reuse.yml' in '/home/user/dev/intelmq/.github/workflows/reuse.yml' 
DEBU[0000] Found workflow 'ansible-playbook.yml' in '/home/user/dev/intelmq/.github/workflows/scripts/ansible-playbook.yml' 
DEBU[0000] Unable to load etag from /home/user/.cache/act/.notices.etag: &{%!e(string=open) %!e(string=/home/user/.cache/act/.notices.etag) %!e(syscall.Errno=2)} 
DEBU[0000] Found workflow 'ansible.sh' in '/home/user/dev/intelmq/.github/workflows/scripts/ansible.sh' 
DEBU[0000] Found workflow 'debian-package.sh' in '/home/user/dev/intelmq/.github/workflows/scripts/debian-package.sh' 
DEBU[0000] Found workflow 'regexploit.sh' in '/home/user/dev/intelmq/.github/workflows/scripts/regexploit.sh' 
DEBU[0000] Found workflow 'setup-full.sh' in '/home/user/dev/intelmq/.github/workflows/scripts/setup-full.sh' 
DEBU[0000] Found workflow 'unittests.yml' in '/home/user/dev/intelmq/.github/workflows/unittests.yml' 
DEBU[0000] Reading workflow '/home/user/dev/intelmq/.github/workflows/ansible-tests.yml' 
DEBU[0000] Reading workflow '/home/user/dev/intelmq/.github/workflows/build-docs.yml' 
DEBU[0000] Reading workflow '/home/user/dev/intelmq/.github/workflows/codeql-analysis.yml' 
DEBU[0000] Reading workflow '/home/user/dev/intelmq/.github/workflows/codespell.yml' 
DEBU[0000] Reading workflow '/home/user/dev/intelmq/.github/workflows/debian-package.yml' 
DEBU[0000] Reading workflow '/home/user/dev/intelmq/.github/workflows/docker.yml' 
DEBU[0000] Reading workflow '/home/user/dev/intelmq/.github/workflows/pycodestyle.yml' 
DEBU[0000] Reading workflow '/home/user/dev/intelmq/.github/workflows/regexploit.yml' 
DEBU[0000] Reading workflow '/home/user/dev/intelmq/.github/workflows/reuse.yml' 
DEBU[0000] Reading workflow '/home/user/dev/intelmq/.github/workflows/scripts/ansible-playbook.yml' 
Error: workflow is not valid. 'ansible-playbook.yml': yaml: unmarshal errors:
  line 5: cannot unmarshal !!seq into model.Workflow

Additional information

No response

Originally created by @sebix on GitHub (May 10, 2023). Original GitHub issue: https://github.com/nektos/act/issues/1795 ### Bug report info ```plain text act version: 0.2.45 GOOS: linux GOARCH: amd64 NumCPU: 8 Docker host: DOCKER_HOST environment variable is not set Sockets found: /var/run/docker.sock Config files: /home/sebastianw/.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.18.10 Module path: github.com/nektos/act Main version: (devel) Main path: github.com/nektos/act Main checksum: Build settings: -compiler: gc -ldflags: -s -w -X main.version=0.2.45 -X main.commit=f1df2ca5d6b315935cf9bb0d2a989175adf4e894 -X main.date=2023-05-01T02:18:49Z -X main.builtBy=goreleaser CGO_ENABLED: 0 GOARCH: amd64 GOOS: linux GOAMD64: v1 vcs: git vcs.revision: f1df2ca5d6b315935cf9bb0d2a989175adf4e894 vcs.time: 2023-05-01T02:18:34Z vcs.modified: false Docker Engine: Engine version: 23.0.5-ce Engine runtime: runc Cgroup version: 2 Cgroup driver: systemd Storage driver: btrfs Registry URI: https://index.docker.io/v1/ OS: openSUSE Tumbleweed OS type: linux OS version: 20230508 OS arch: x86_64 OS kernel: 6.3.1-1-default OS CPU: 8 OS memory: 31880 MB Security options: name=apparmor name=seccomp,profile=builtin name=cgroupns ``` ### Command used with act ```sh act -l ``` ### Describe issue This is the actual output: ``` Error: workflow is not valid. 'ansible-playbook.yml': yaml: unmarshal errors: line 5: cannot unmarshal !!seq into model.Workflow ``` But I expect that workflows are listed like ``` Stage Job ID Job name Workflow name Workflow file Events 0 ansible Run ansible tests Run ansible tests ansible-tests.yml push,pull_request ... ``` The issue is the file `.github/workflows/scripts/ansible-playbook.yml` which is not a workflow file, but act tries to parse it as a workflow file although it isn't placed in the workflow directory. These workflows work on GitHub, see: https://github.com/certtools/intelmq/actions/ ### Link to GitHub repository github.com/certtools/intelmq/ ### Workflow content ```yml #Github Workflow to run ansible tests # #SPDX-FileCopyrightText: 2021 Birger Schacht <schacht@cert.at> #SPDX-License-Identifier: AGPL-3.0-or-later # name: "Run ansible tests" on: push: branches: [develop, maintenance, master] paths-ignore: - '.github/**' pull_request: branches: [develop, maintenance] paths-ignore: - '.github/**' jobs: ansible: # temporary fix for https://github.com/actions/virtual-environments/issues/3080 runs-on: ubuntu-22.04 name: Run ansible tests steps: - name: Checkout repository uses: actions/checkout@v2 with: path: ./src/intelmq - name: Checkout ansible scripts uses: actions/checkout@v2 with: repository: certtools/intelmq-vagrant path: ./src/intelmq-vagrant - run: apt update && apt install -y podman - name: Run ansible tests run: podman run -e CI=${CI} -v ${GITHUB_WORKSPACE}/src:/src docker.io/debian:buster-slim /src/intelmq/.github/workflows/scripts/ansible.sh ``` ### Relevant log output ```sh DEBU[0000] Loading environment from /home/user/dev/intelmq/.env DEBU[0000] Loading action inputs from /home/user/dev/intelmq/.input DEBU[0000] Loading secrets from /home/user/dev/intelmq/.secrets DEBU[0000] Evaluated matrix inclusions: map[] DEBU[0000] Loading workflows from '/home/user/dev/intelmq/.github/workflows' DEBU[0000] Loading workflows recursively DEBU[0000] Found workflow 'ansible-tests.yml' in '/home/user/dev/intelmq/.github/workflows/ansible-tests.yml' DEBU[0000] Found workflow 'build-docs.yml' in '/home/user/dev/intelmq/.github/workflows/build-docs.yml' DEBU[0000] Found workflow 'codeql-analysis.yml' in '/home/user/dev/intelmq/.github/workflows/codeql-analysis.yml' DEBU[0000] Found workflow 'codespell.excludelines' in '/home/user/dev/intelmq/.github/workflows/codespell.excludelines' DEBU[0000] Found workflow 'codespell.yml' in '/home/user/dev/intelmq/.github/workflows/codespell.yml' DEBU[0000] Found workflow 'debian-package.yml' in '/home/user/dev/intelmq/.github/workflows/debian-package.yml' DEBU[0000] Found workflow 'docker.yml' in '/home/user/dev/intelmq/.github/workflows/docker.yml' DEBU[0000] Found workflow 'pycodestyle.yml' in '/home/user/dev/intelmq/.github/workflows/pycodestyle.yml' DEBU[0000] Found workflow 'github.py' in '/home/user/dev/intelmq/.github/workflows/python/github.py' DEBU[0000] Found workflow 'pycodestyle_comment.py' in '/home/user/dev/intelmq/.github/workflows/python/pycodestyle_comment.py' DEBU[0000] Found workflow 'regexploit.yml' in '/home/user/dev/intelmq/.github/workflows/regexploit.yml' DEBU[0000] Found workflow 'reuse.yml' in '/home/user/dev/intelmq/.github/workflows/reuse.yml' DEBU[0000] Found workflow 'ansible-playbook.yml' in '/home/user/dev/intelmq/.github/workflows/scripts/ansible-playbook.yml' DEBU[0000] Unable to load etag from /home/user/.cache/act/.notices.etag: &{%!e(string=open) %!e(string=/home/user/.cache/act/.notices.etag) %!e(syscall.Errno=2)} DEBU[0000] Found workflow 'ansible.sh' in '/home/user/dev/intelmq/.github/workflows/scripts/ansible.sh' DEBU[0000] Found workflow 'debian-package.sh' in '/home/user/dev/intelmq/.github/workflows/scripts/debian-package.sh' DEBU[0000] Found workflow 'regexploit.sh' in '/home/user/dev/intelmq/.github/workflows/scripts/regexploit.sh' DEBU[0000] Found workflow 'setup-full.sh' in '/home/user/dev/intelmq/.github/workflows/scripts/setup-full.sh' DEBU[0000] Found workflow 'unittests.yml' in '/home/user/dev/intelmq/.github/workflows/unittests.yml' DEBU[0000] Reading workflow '/home/user/dev/intelmq/.github/workflows/ansible-tests.yml' DEBU[0000] Reading workflow '/home/user/dev/intelmq/.github/workflows/build-docs.yml' DEBU[0000] Reading workflow '/home/user/dev/intelmq/.github/workflows/codeql-analysis.yml' DEBU[0000] Reading workflow '/home/user/dev/intelmq/.github/workflows/codespell.yml' DEBU[0000] Reading workflow '/home/user/dev/intelmq/.github/workflows/debian-package.yml' DEBU[0000] Reading workflow '/home/user/dev/intelmq/.github/workflows/docker.yml' DEBU[0000] Reading workflow '/home/user/dev/intelmq/.github/workflows/pycodestyle.yml' DEBU[0000] Reading workflow '/home/user/dev/intelmq/.github/workflows/regexploit.yml' DEBU[0000] Reading workflow '/home/user/dev/intelmq/.github/workflows/reuse.yml' DEBU[0000] Reading workflow '/home/user/dev/intelmq/.github/workflows/scripts/ansible-playbook.yml' Error: workflow is not valid. 'ansible-playbook.yml': yaml: unmarshal errors: line 5: cannot unmarshal !!seq into model.Workflow ``` ### Additional information _No response_
kerem 2026-03-01 21:47:05 +03:00
kerem commented 2026-03-01 21:47:06 +03:00
Author
Owner
Copy link

@ChristopherHX commented on GitHub (May 10, 2023):

I wondered why recursively loading of workflows was ever merged into act (I didn't had the permission to block that), you can unblock your issue with the flag --no-recurse.

act -l --no-recurse

I don't think it is best practice to store non workflow files under .github/workflows/**/*, because this .github folder may introduce new config file locations at any point of time.

Do you want to open a PR to set the default value of the flag to true? github.com/nektos/act@65ef31f102/cmd/root.go (L73)

You would only need to replace false with true.

<!-- gh-comment-id:1541610610 --> @ChristopherHX commented on GitHub (May 10, 2023): I wondered why recursively loading of workflows was ever merged into act (I didn't had the permission to block that), you can unblock your issue with the flag `--no-recurse`. `act -l --no-recurse` I don't think it is best practice to store non workflow files under `.github/workflows/**/*`, because this `.github` folder may introduce new config file locations at any point of time. Do you want to open a PR to set the default value of the flag to true? https://github.com/nektos/act/blob/65ef31f102ceb75623973921099454637bab55b0/cmd/root.go#L73 You would only need to replace `false` with `true`.
kerem commented 2026-03-01 21:47:06 +03:00
Author
Owner
Copy link

@sebix commented on GitHub (May 10, 2023):

As long as GitHub itself does not load workflows recursively, I don't think it's adequate to do it in act for consistency.

<!-- gh-comment-id:1542704679 --> @sebix commented on GitHub (May 10, 2023): As long as GitHub itself does not load workflows recursively, I don't think it's adequate to do it in `act` for consistency.
kerem commented 2026-03-01 21:47:06 +03:00
Author
Owner
Copy link

@JoshMcCullough commented on GitHub (May 15, 2023):

For this issue, it seems like (as suggested above) non-workflow files shouldn't be stored under .github/workflows. Instead, the should live somewhere else in the repo and be referenced from the workflows.

<!-- gh-comment-id:1548474353 --> @JoshMcCullough commented on GitHub (May 15, 2023): For this issue, it seems like (as suggested above) non-workflow files shouldn't be stored under `.github/workflows`. Instead, the should live somewhere else in the repo and be referenced from the workflows.
kerem commented 2026-03-01 21:47:06 +03:00
Author
Owner
Copy link

@github-actions[bot] commented on GitHub (Nov 12, 2023):

Issue is stale and will be closed in 14 days unless there is new activity

<!-- gh-comment-id:1806951186 --> @github-actions[bot] commented on GitHub (Nov 12, 2023): Issue is stale and will be closed in 14 days unless there is new activity
kerem commented 2026-03-01 21:47:06 +03:00
Author
Owner
Copy link

@dezren39 commented on GitHub (Nov 16, 2023):

For this issue, it seems like (as suggested above) non-workflow files shouldn't be stored under .github/workflows. Instead, the should live somewhere else in the repo and be referenced from the workflows.

this isn't documented in github, it's probably a best practice of sorts not to do this, but it's common to see variations in how people use the workflows folder. sort of like 'things in .github/workflows are build stuff, the rest is the "real code"'. i don't subscribe to that personally, but i've had multiple experiences (mostly in enterprise) where this has occurred. I suggest that, where possible, act should try to avoid putting additional constraints on users that github actions doesn't have.

<!-- gh-comment-id:1813564200 --> @dezren39 commented on GitHub (Nov 16, 2023): > For this issue, it seems like (as suggested above) non-workflow files shouldn't be stored under `.github/workflows`. Instead, the should live somewhere else in the repo and be referenced from the workflows. this isn't documented in github, it's probably a best practice of sorts not to do this, but it's common to see variations in how people use the workflows folder. sort of like 'things in .github/workflows are build stuff, the rest is the "real code"'. i don't subscribe to that personally, but i've had multiple experiences (mostly in enterprise) where this has occurred. I suggest that, where possible, act should try to avoid putting additional constraints on users that github actions doesn't have.
kerem commented 2026-03-01 21:47:06 +03:00
Author
Owner
Copy link

@github-actions[bot] commented on GitHub (May 15, 2024):

Issue is stale and will be closed in 14 days unless there is new activity

<!-- gh-comment-id:2111356803 --> @github-actions[bot] commented on GitHub (May 15, 2024): Issue is stale and will be closed in 14 days unless there is new activity
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
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#874
No description provided.