Format files #13698
No reviewers
Labels
No Label
backport/done
backport/v1.0
backport/v1.1
backport/v1.10
backport/v1.11
backport/v1.12
backport/v1.13
backport/v1.14
backport/v1.15
backport/v1.2
backport/v1.3
backport/v1.4
backport/v1.5
backport/v1.6
backport/v1.7
backport/v1.8
backport/v1.9
bounty
changelog
dependencies
frontport/done
frontport/main
good first issue
Hacktoberfest
hacktoberfest-accepted
in progress
kind/api
kind/breaking
kind/bug
kind/build
kind/deployment
kind/deprecated
kind/docs
kind/enhancement
kind/feature
kind/lint
kind/misc
kind/moderation
kind/package
kind/proposal
kind/question
kind/refactor
kind/regression
kind/security
kind/summary
kind/testing
kind/translation
kind/ui
kind/upstream-related
kind/usability
kind/ux
lgtm/done
lgtm/need 1
lgtm/need 2
performance/bigrepo
performance/cpu
performance/memory
performance/speed
priority/critical
priority/low
priority/maybe
priority/medium
proposal/rejected
reviewed/confirmed
reviewed/duplicate
reviewed/fixed
reviewed/invalid
reviewed/not-a-bug
reviewed/wontfix
skip-changelog
stale
status/blocked
status/needs-feedback
status/wip
theme/2fa
theme/authentication
theme/avatar
theme/backup-restore
theme/docker
theme/federation
theme/issues
theme/kanban
theme/markdown
theme/migration
theme/mobile
theme/pr
theme/signing
theme/sqlite
theme/timetracker
theme/webhook
theme/wiki
No Milestone
No project
No Assignees
2 Participants
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: lunny/gitea#13698
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "format-files"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
as title ...
It's anoing to see many lines of diff if you edit one of this files and the editor automaticaly correct unrelated things.
this pull format files so there will be less + fix alignment of "make help"
this pull does not change any behaviour
May want to merge this file with the one in root (and update any files in
docs
to conform).I don't particularily like this style of spacing and we don't do it in JS either. Maybe rename to
.eslintrc.yaml
to see if that shuts up your tool?Is it really an issue? eslint certainly doesn't complain about it.
it's not - the importand thing for me was about markdown and ini files :)
@silverwind is
.eslintrc.yaml
supported by our js linter?never mind ... it does not work anyway ... - reverting
@silverwind done
Ident size 8 imho is way too much ?
For javascript most defaults to 2 spaces identing
.eslintrc.yaml
should generally work except for maybe some outdated editor integrations which is the reason I generally use the older.eslintrc
.That section can just be removed, we use size 2 for go since a while now inherited from
[*]
.I'd remove this as well and reindent matching files in
docs
. The other formats should already be at 2-space outside that folder.Remove as well, I remember specifically removing this advertisment ?