Fix creating user token during the registration process when both Token authentication and Session authentication are used simultaneously #84
Workflow file for this run
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| name: 'Automatically close stale issues and PRs' | ||
| on: | ||
| schedule: | ||
| - cron: '0 0 * * *' | ||
| jobs: | ||
| stale: | ||
| runs-on: ubuntu-latest | ||
| steps: | ||
| - uses: actions/stale@v5 | ||
| with: | ||
| # Number of days of inactivity before an issue becomes stale | ||
| daysUntilStale: 60 | ||
| # Number of days of inactivity before a stale issue is closed | ||
| daysUntilClose: 7 | ||
| # Issues with these labels will never be considered stale | ||
| exemptLabels: | ||
| - pinned | ||
| - security | ||
| # Label to use when marking an issue as stale | ||
| staleLabel: wontfix | ||
| # Comment to post when marking an issue as stale. Set to `false` to disable | ||
| markComment: > | ||
| This issue has been automatically marked as stale because it has not had | ||
| recent activity. It will be closed if no further activity occurs. Thank you | ||
| for your contributions. | ||
| # Comment to post when closing a stale issue. Set to `false` to disable | ||
| closeComment: false | ||
