Skip to content

Add configuration option to disable check of "This file contains ambiguous Unicode characters!" #24483

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

Closed
sgabenov opened this issue May 2, 2023 · 0 comments · Fixed by #28454
Labels
type/feature Completely new functionality. Can only be merged if feature freeze is not active. type/proposal The new feature has not been accepted yet but needs to be discussed first.

Comments

@sgabenov
Copy link

sgabenov commented May 2, 2023

Feature Description

There should be a configuration option to disable check of "This file contains ambiguous Unicode characters!"
Our project has different language comments and it triggers this banner to be displayed on every file. Whant to have a possibility to disable it

Screenshots

chars

@sgabenov sgabenov added type/feature Completely new functionality. Can only be merged if feature freeze is not active. type/proposal The new feature has not been accepted yet but needs to be discussed first. labels May 2, 2023
lunny pushed a commit that referenced this issue Dec 17, 2023

Verified

This commit was signed with the committer’s verified signature.
lunny Lunny Xiao
* Close #24483
* Close #28123
* Close #23682
* Close #23149

(maybe more)
wxiaoguang added a commit to wxiaoguang/gitea that referenced this issue Dec 17, 2023

Verified

This commit was signed with the committer’s verified signature.
lunny Lunny Xiao
…a#28454)

* Close go-gitea#24483
* Close go-gitea#28123
* Close go-gitea#23682
* Close go-gitea#23149

(maybe more)
wolfogre pushed a commit that referenced this issue Dec 18, 2023

Verified

This commit was signed with the committer’s verified signature.
lunny Lunny Xiao
…#28499)

Backport #28454 (the only conflict is caused by some comments)

* Close #24483
* Close #28123
* Close #23682
* Close #23149
fuxiaohei pushed a commit to fuxiaohei/gitea that referenced this issue Jan 17, 2024

Verified

This commit was signed with the committer’s verified signature.
lunny Lunny Xiao
…a#28454)

* Close go-gitea#24483
* Close go-gitea#28123
* Close go-gitea#23682
* Close go-gitea#23149

(maybe more)
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Feb 1, 2024
silverwind pushed a commit to silverwind/gitea that referenced this issue Feb 20, 2024
project-mirrors-bot-tu bot pushed a commit to project-mirrors/forgejo-as-gitea-fork that referenced this issue Jan 23, 2025

Verified

This commit was signed with the committer’s verified signature.
lunny Lunny Xiao
…a#28454) (go-gitea#28499)

Backport go-gitea#28454 (the only conflict is caused by some comments)

* Close go-gitea#24483
* Close go-gitea#28123
* Close go-gitea#23682
* Close go-gitea#23149

(cherry picked from commit a3f403f)

Conflicts:
	modules/setting/ui.go
	trivial context conflict
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
type/feature Completely new functionality. Can only be merged if feature freeze is not active. type/proposal The new feature has not been accepted yet but needs to be discussed first.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant