Skip to content
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

Typo inside Camo#Allways #31575

Closed
litetex opened this issue Jul 5, 2024 · 4 comments · Fixed by #32097
Closed

Typo inside Camo#Allways #31575

litetex opened this issue Jul 5, 2024 · 4 comments · Fixed by #32097
Labels

Comments

@litetex
Copy link

litetex commented Jul 5, 2024

Description

The value of Camo#Allways seems to have a typo. It should be Camo#Always with one l.

Can be found here:
https://github.com/search?q=repo%3Ago-gitea%2Fgitea%20ALLWAYS&type=code

@charles7668
Copy link
Contributor

I don't think this is a typo. In this configuration context, "ALLWays" might mean "all_ways".

@lunny
Copy link
Member

lunny commented Aug 14, 2024

Close as @charles7668 's feedback.

@lunny lunny closed this as not planned Won't fix, can't repro, duplicate, stale Aug 14, 2024
@lunny lunny added issue/not-a-bug The reported issue is the intended behavior or the problem is not inside Gitea and removed type/bug labels Aug 14, 2024
@wxiaoguang
Copy link
Contributor

But it is indeed a typo. all_ways should be ALL_WAYS according to the naming style (underline between words).

@lunny lunny reopened this Aug 14, 2024
@lunny lunny added type/bug and removed issue/not-a-bug The reported issue is the intended behavior or the problem is not inside Gitea labels Aug 14, 2024
@SuperSandro2000
Copy link
Contributor

Since gitea has no strict config validation, it is really easy to miss configure this.

@go-gitea go-gitea locked as resolved and limited conversation to collaborators Dec 20, 2024
project-mirrors-bot-tu bot pushed a commit to project-mirrors/forgejo-as-gitea-fork that referenced this issue Jan 23, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants