-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Invalid OLDER_THAN values in "Extended cron tasks" docs #20868
Labels
Comments
silverwind
pushed a commit
that referenced
this issue
May 13, 2023
…24695) Looks like a copy-paste leftover - Fixes #20868 Co-authored-by: Giteabot <[email protected]>
GiteaBot
added a commit
to GiteaBot/gitea
that referenced
this issue
May 13, 2023
…o-gitea#24695) Looks like a copy-paste leftover - Fixes go-gitea#20868 Co-authored-by: Giteabot <[email protected]>
lunny
pushed a commit
that referenced
this issue
May 13, 2023
…24695) (#24698) Backport #24695 by @yardenshoham Looks like a copy-paste leftover - Fixes #20868 Co-authored-by: Yarden Shoham <[email protected]>
Codeberg-org
pushed a commit
to Codeberg-org/gitea
that referenced
this issue
Jun 3, 2023
…o-gitea#24695) (go-gitea#24698) Backport go-gitea#24695 by @yardenshoham Looks like a copy-paste leftover - Fixes go-gitea#20868 Co-authored-by: Yarden Shoham <[email protected]> (cherry picked from commit aa984f2)
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Description
I found similar mistakes in cheat sheet's "Extended cron tasks" section in which OLDER_THAN of both cron.delete_old_actions and cron.delete_old_system_notices contain invalid
@every
keyword. app.example.ini has correct configurations however.Hope this will be fixed soon, as the tasks are still marked as finished in the monitoring tab without warnings/errors.
Gitea Version
1.17.1
Can you reproduce the bug on the Gitea demo site?
No
Log Gist
No response
Screenshots
No response
Git Version
2.17.1
Operating System
Ubuntu 18.04.6 LTS
How are you running Gitea?
Irrelevant
Database
PostgreSQL
The text was updated successfully, but these errors were encountered: