no-response.yaml

name: No Response

# Both `issue_comment` and `scheduled` event types are required for this Action
# to work properly.
on:
  issue_comment:
    types: [created]
  schedule:
    # Schedule for everyday for 1 minute after midnight
    - cron: "1 0 * * *"

# By specifying the access of one of the scopes, all of those that are not
# specified are set to 'none'.
permissions:
  issues: write

jobs:
  noResponse:
    runs-on: ubuntu-latest
    if: ${{ github.repository == 'googleads/googleads-mobile-flutter' }}
    steps:
      - uses: lee-dohm/no-response@v0.5.0
        with:
          token: ${{ github.token }}
          # Comment to post when closing an Issue for lack of response. Set to `false` to disable
          closeComment: >
            Without additional information, I am unfortunately not sure how to
            resolve this issue. I am therefore reluctantly going to close this
            bug for now.
            If you still encounter the issue or have more information, please feel free to share it here and I will be happy to reopen the issue.
            Thanks for your contribution.
          # Number of days of inactivity before an issue is closed for lack of response.
          daysUntilClose: 60
          # Label requiring a response.
          responseRequiredLabel: "waiting for author"