Unexpected behavior of stale workflow

[helenakallekleiv]

Module Name

baseline

Module Version

latest

Terraform Version

latest

Description

Daily actions workflow does not process the issues correctly. The workflow runs as it should, but we recieve a warning shown in the image below. We discovered that the expected behavior of adding/removing the stale label to issues and PRs with inactivity/activity does not currently behave as expected.

In four separate issues, the workflow added the stale label due to inactivity, but did not close the issues after the cofigured days of inactivity were up. Adding activity to the issue via comment, did not trigger the workflow to remove the stale label either.

Issues:

• Do we keep the Container App module or archive it? #131
• Clarify goal of baseline modules #53
• Don't create conditional resources based on values that are unknown during planning #119
• Enforce Entra ID admin for PostgreSQL servers #123

The warning shown below has been present since this run.

The common demoninator is that all of the issues in question has the github-actions bot message:

Here, it states that the cofigured days of inactivity is 14, which is the original configured days, before we changed it to 7.

Example Terraform Configuration

No response

Steps to Reproduce

No response

[github-actions]

There has been no activity on this issue for 60 days. stale label will be added. If no additional activity occurs, the issue will be closed in 7 days.

[github-actions]

There has been no activity on this issue for 60 days. stale label will be added. If no additional activity occurs, the issue will be closed in 7 days.

[github-actions]

There has been no activity on this stale issue for 7 days. This issue will now be closed. If new activity occurs, the issue will reopen.