loading up the forgejo repo on tangled to test page performance
0
fork

Configure Feed

Select the types of activity you want to include in your feed.

Add `yamllint` (#26965)

So that https://github.com/go-gitea/gitea/pull/26964 does not happen
again. Merge this after that PR. Config is based on
[node's](https://github.com/nodejs/node/blob/main/.yamllint.yaml).

---------

Co-authored-by: techknowlogick <techknowlogick@gitea.com>

authored by

silverwind
techknowlogick
and committed by
GitHub
3c0c2796 f9abb6ad

+281 -187
+9 -9
.drone.yml
··· 154 154 when: 155 155 event: 156 156 exclude: 157 - - pull_request 157 + - pull_request 158 158 159 159 - name: publish-rootless 160 160 image: plugins/docker:latest ··· 176 176 when: 177 177 event: 178 178 exclude: 179 - - pull_request 179 + - pull_request 180 180 --- 181 181 182 182 kind: pipeline ··· 220 220 when: 221 221 event: 222 222 exclude: 223 - - pull_request 223 + - pull_request 224 224 225 225 - name: publish-rootless 226 226 image: plugins/docker:latest ··· 241 241 when: 242 242 event: 243 243 exclude: 244 - - pull_request 244 + - pull_request 245 245 246 246 --- 247 247 kind: pipeline ··· 289 289 when: 290 290 event: 291 291 exclude: 292 - - pull_request 292 + - pull_request 293 293 294 294 - name: publish-rootless 295 295 image: plugins/docker:latest ··· 311 311 when: 312 312 event: 313 313 exclude: 314 - - pull_request 314 + - pull_request 315 315 316 316 --- 317 317 kind: pipeline ··· 355 355 when: 356 356 event: 357 357 exclude: 358 - - pull_request 358 + - pull_request 359 359 360 360 - name: publish-rootless 361 361 image: plugins/docker:latest ··· 376 376 when: 377 377 event: 378 378 exclude: 379 - - pull_request 379 + - pull_request 380 380 381 381 --- 382 382 kind: pipeline ··· 413 413 414 414 trigger: 415 415 ref: 416 - - "refs/tags/**" 416 + - "refs/tags/**" 417 417 paths: 418 418 exclude: 419 419 - "docs/**"
+1 -1
.eslintrc.yaml
··· 156 156 import/no-restricted-paths: [0] 157 157 import/no-self-import: [2] 158 158 import/no-unassigned-import: [0] 159 - import/no-unresolved: [2, {commonjs: true, ignore: [\?.+$, ^vitest/]}] 159 + import/no-unresolved: [2, {commonjs: true, ignore: ["\\?.+$", ^vitest/]}] 160 160 import/no-unused-modules: [2, {unusedExports: true}] 161 161 import/no-useless-path-segments: [2, {commonjs: true}] 162 162 import/no-webpack-loader-syntax: [2]
+87 -87
.github/ISSUE_TEMPLATE/bug-report.yaml
··· 2 2 description: Found something you weren't expecting? Report it here! 3 3 labels: ["kind/bug"] 4 4 body: 5 - - type: markdown 6 - attributes: 7 - value: | 8 - NOTE: If your issue is a security concern, please send an email to security@gitea.io instead of opening a public issue. 9 - - type: markdown 10 - attributes: 11 - value: | 12 - 1. Please speak English, this is the language all maintainers can speak and write. 13 - 2. Please ask questions or configuration/deploy problems on our Discord 14 - server (https://discord.gg/gitea) or forum (https://discourse.gitea.io). 15 - 3. Make sure you are using the latest release and 16 - take a moment to check that your issue hasn't been reported before. 17 - 4. Make sure it's not mentioned in the FAQ (https://docs.gitea.com/help/faq) 18 - 5. It's really important to provide pertinent details and logs (https://docs.gitea.com/help/support), 19 - incomplete details will be handled as an invalid report. 20 - - type: textarea 21 - id: description 22 - attributes: 23 - label: Description 24 - description: | 25 - Please provide a description of your issue here, with a URL if you were able to reproduce the issue (see below) 26 - If you are using a proxy or a CDN (e.g. Cloudflare) in front of Gitea, please disable the proxy/CDN fully and access Gitea directly to confirm the issue still persists without those services. 27 - - type: input 28 - id: gitea-ver 29 - attributes: 30 - label: Gitea Version 31 - description: Gitea version (or commit reference) of your instance 32 - validations: 33 - required: true 34 - - type: dropdown 35 - id: can-reproduce 36 - attributes: 37 - label: Can you reproduce the bug on the Gitea demo site? 38 - description: | 39 - If so, please provide a URL in the Description field 40 - URL of Gitea demo: https://try.gitea.io 41 - options: 42 - - "Yes" 43 - - "No" 44 - validations: 45 - required: true 46 - - type: markdown 47 - attributes: 48 - value: | 49 - It's really important to provide pertinent logs 50 - Please read https://docs.gitea.com/administration/logging-config#collecting-logs-for-help 51 - In addition, if your problem relates to git commands set `RUN_MODE=dev` at the top of app.ini 52 - - type: input 53 - id: logs 54 - attributes: 55 - label: Log Gist 56 - description: Please provide a gist URL of your logs, with any sensitive information (e.g. API keys) removed/hidden 57 - - type: textarea 58 - id: screenshots 59 - attributes: 60 - label: Screenshots 61 - description: If this issue involves the Web Interface, please provide one or more screenshots 62 - - type: input 63 - id: git-ver 64 - attributes: 65 - label: Git Version 66 - description: The version of git running on the server 67 - - type: input 68 - id: os-ver 69 - attributes: 70 - label: Operating System 71 - description: The operating system you are using to run Gitea 72 - - type: textarea 73 - id: run-info 74 - attributes: 75 - label: How are you running Gitea? 76 - description: | 77 - Please include information on whether you built Gitea yourself, used one of our downloads, are using https://try.gitea.io or are using some other package 78 - Please also tell us how you are running Gitea, e.g. if it is being run from docker, a command-line, systemd etc. 79 - If you are using a package or systemd tell us what distribution you are using 80 - validations: 81 - required: true 82 - - type: dropdown 83 - id: database 84 - attributes: 85 - label: Database 86 - description: What database system are you running? 87 - options: 88 - - PostgreSQL 89 - - MySQL/MariaDB 90 - - MSSQL 91 - - SQLite 5 + - type: markdown 6 + attributes: 7 + value: | 8 + NOTE: If your issue is a security concern, please send an email to security@gitea.io instead of opening a public issue. 9 + - type: markdown 10 + attributes: 11 + value: | 12 + 1. Please speak English, this is the language all maintainers can speak and write. 13 + 2. Please ask questions or configuration/deploy problems on our Discord 14 + server (https://discord.gg/gitea) or forum (https://discourse.gitea.io). 15 + 3. Make sure you are using the latest release and 16 + take a moment to check that your issue hasn't been reported before. 17 + 4. Make sure it's not mentioned in the FAQ (https://docs.gitea.com/help/faq) 18 + 5. It's really important to provide pertinent details and logs (https://docs.gitea.com/help/support), 19 + incomplete details will be handled as an invalid report. 20 + - type: textarea 21 + id: description 22 + attributes: 23 + label: Description 24 + description: | 25 + Please provide a description of your issue here, with a URL if you were able to reproduce the issue (see below) 26 + If you are using a proxy or a CDN (e.g. Cloudflare) in front of Gitea, please disable the proxy/CDN fully and access Gitea directly to confirm the issue still persists without those services. 27 + - type: input 28 + id: gitea-ver 29 + attributes: 30 + label: Gitea Version 31 + description: Gitea version (or commit reference) of your instance 32 + validations: 33 + required: true 34 + - type: dropdown 35 + id: can-reproduce 36 + attributes: 37 + label: Can you reproduce the bug on the Gitea demo site? 38 + description: | 39 + If so, please provide a URL in the Description field 40 + URL of Gitea demo: https://try.gitea.io 41 + options: 42 + - "Yes" 43 + - "No" 44 + validations: 45 + required: true 46 + - type: markdown 47 + attributes: 48 + value: | 49 + It's really important to provide pertinent logs 50 + Please read https://docs.gitea.com/administration/logging-config#collecting-logs-for-help 51 + In addition, if your problem relates to git commands set `RUN_MODE=dev` at the top of app.ini 52 + - type: input 53 + id: logs 54 + attributes: 55 + label: Log Gist 56 + description: Please provide a gist URL of your logs, with any sensitive information (e.g. API keys) removed/hidden 57 + - type: textarea 58 + id: screenshots 59 + attributes: 60 + label: Screenshots 61 + description: If this issue involves the Web Interface, please provide one or more screenshots 62 + - type: input 63 + id: git-ver 64 + attributes: 65 + label: Git Version 66 + description: The version of git running on the server 67 + - type: input 68 + id: os-ver 69 + attributes: 70 + label: Operating System 71 + description: The operating system you are using to run Gitea 72 + - type: textarea 73 + id: run-info 74 + attributes: 75 + label: How are you running Gitea? 76 + description: | 77 + Please include information on whether you built Gitea yourself, used one of our downloads, are using https://try.gitea.io or are using some other package 78 + Please also tell us how you are running Gitea, e.g. if it is being run from docker, a command-line, systemd etc. 79 + If you are using a package or systemd tell us what distribution you are using 80 + validations: 81 + required: true 82 + - type: dropdown 83 + id: database 84 + attributes: 85 + label: Database 86 + description: What database system are you running? 87 + options: 88 + - PostgreSQL 89 + - MySQL/MariaDB 90 + - MSSQL 91 + - SQLite
+20 -20
.github/ISSUE_TEMPLATE/feature-request.yaml
··· 2 2 description: Got an idea for a feature that Gitea doesn't have currently? Submit your idea here! 3 3 labels: ["kind/proposal"] 4 4 body: 5 - - type: markdown 6 - attributes: 7 - value: | 8 - 1. Please speak English, this is the language all maintainers can speak and write. 9 - 2. Please ask questions or configuration/deploy problems on our Discord 10 - server (https://discord.gg/gitea) or forum (https://discourse.gitea.io). 11 - 3. Please take a moment to check that your feature hasn't already been suggested. 12 - - type: textarea 13 - id: description 14 - attributes: 15 - label: Feature Description 16 - placeholder: | 17 - I think it would be great if Gitea had... 18 - validations: 19 - required: true 20 - - type: textarea 21 - id: screenshots 22 - attributes: 23 - label: Screenshots 24 - description: If you can, provide screenshots of an implementation on another site e.g. GitHub 5 + - type: markdown 6 + attributes: 7 + value: | 8 + 1. Please speak English, this is the language all maintainers can speak and write. 9 + 2. Please ask questions or configuration/deploy problems on our Discord 10 + server (https://discord.gg/gitea) or forum (https://discourse.gitea.io). 11 + 3. Please take a moment to check that your feature hasn't already been suggested. 12 + - type: textarea 13 + id: description 14 + attributes: 15 + label: Feature Description 16 + placeholder: | 17 + I think it would be great if Gitea had... 18 + validations: 19 + required: true 20 + - type: textarea 21 + id: screenshots 22 + attributes: 23 + label: Screenshots 24 + description: If you can, provide screenshots of an implementation on another site e.g. GitHub
+62 -62
.github/ISSUE_TEMPLATE/ui.bug-report.yaml
··· 2 2 description: Something doesn't look quite as it should? Report it here! 3 3 labels: ["kind/bug", "kind/ui"] 4 4 body: 5 - - type: markdown 6 - attributes: 7 - value: | 8 - NOTE: If your issue is a security concern, please send an email to security@gitea.io instead of opening a public issue. 9 - - type: markdown 10 - attributes: 11 - value: | 12 - 1. Please speak English, this is the language all maintainers can speak and write. 13 - 2. Please ask questions or configuration/deploy problems on our Discord 14 - server (https://discord.gg/gitea) or forum (https://discourse.gitea.io). 15 - 3. Please take a moment to check that your issue doesn't already exist. 16 - 4. Make sure it's not mentioned in the FAQ (https://docs.gitea.com/help/faq) 17 - 5. Please give all relevant information below for bug reports, because 18 - incomplete details will be handled as an invalid report. 19 - 6. In particular it's really important to provide pertinent logs. If you are certain that this is a javascript 20 - error, show us the javascript console. If the error appears to relate to Gitea the server you must also give us 21 - DEBUG level logs. (See https://docs.gitea.com/administration/logging-config#collecting-logs-for-help) 22 - - type: textarea 23 - id: description 24 - attributes: 25 - label: Description 26 - description: | 27 - Please provide a description of your issue here, with a URL if you were able to reproduce the issue (see below) 28 - If using a proxy or a CDN (e.g. CloudFlare) in front of gitea, please disable the proxy/CDN fully and connect to gitea directly to confirm the issue still persists without those services. 29 - - type: textarea 30 - id: screenshots 31 - attributes: 32 - label: Screenshots 33 - description: Please provide at least 1 screenshot showing the issue. 34 - validations: 35 - required: true 36 - - type: input 37 - id: gitea-ver 38 - attributes: 39 - label: Gitea Version 40 - description: Gitea version (or commit reference) your instance is running 41 - validations: 42 - required: true 43 - - type: dropdown 44 - id: can-reproduce 45 - attributes: 46 - label: Can you reproduce the bug on the Gitea demo site? 47 - description: | 48 - If so, please provide a URL in the Description field 49 - URL of Gitea demo: https://try.gitea.io 50 - options: 51 - - "Yes" 52 - - "No" 53 - validations: 54 - required: true 55 - - type: input 56 - id: os-ver 57 - attributes: 58 - label: Operating System 59 - description: The operating system you are using to access Gitea 60 - - type: input 61 - id: browser-ver 62 - attributes: 63 - label: Browser Version 64 - description: The browser and version that you are using to access Gitea 65 - validations: 66 - required: true 5 + - type: markdown 6 + attributes: 7 + value: | 8 + NOTE: If your issue is a security concern, please send an email to security@gitea.io instead of opening a public issue. 9 + - type: markdown 10 + attributes: 11 + value: | 12 + 1. Please speak English, this is the language all maintainers can speak and write. 13 + 2. Please ask questions or configuration/deploy problems on our Discord 14 + server (https://discord.gg/gitea) or forum (https://discourse.gitea.io). 15 + 3. Please take a moment to check that your issue doesn't already exist. 16 + 4. Make sure it's not mentioned in the FAQ (https://docs.gitea.com/help/faq) 17 + 5. Please give all relevant information below for bug reports, because 18 + incomplete details will be handled as an invalid report. 19 + 6. In particular it's really important to provide pertinent logs. If you are certain that this is a javascript 20 + error, show us the javascript console. If the error appears to relate to Gitea the server you must also give us 21 + DEBUG level logs. (See https://docs.gitea.com/administration/logging-config#collecting-logs-for-help) 22 + - type: textarea 23 + id: description 24 + attributes: 25 + label: Description 26 + description: | 27 + Please provide a description of your issue here, with a URL if you were able to reproduce the issue (see below) 28 + If using a proxy or a CDN (e.g. CloudFlare) in front of gitea, please disable the proxy/CDN fully and connect to gitea directly to confirm the issue still persists without those services. 29 + - type: textarea 30 + id: screenshots 31 + attributes: 32 + label: Screenshots 33 + description: Please provide at least 1 screenshot showing the issue. 34 + validations: 35 + required: true 36 + - type: input 37 + id: gitea-ver 38 + attributes: 39 + label: Gitea Version 40 + description: Gitea version (or commit reference) your instance is running 41 + validations: 42 + required: true 43 + - type: dropdown 44 + id: can-reproduce 45 + attributes: 46 + label: Can you reproduce the bug on the Gitea demo site? 47 + description: | 48 + If so, please provide a URL in the Description field 49 + URL of Gitea demo: https://try.gitea.io 50 + options: 51 + - "Yes" 52 + - "No" 53 + validations: 54 + required: true 55 + - type: input 56 + id: os-ver 57 + attributes: 58 + label: Operating System 59 + description: The operating system you are using to access Gitea 60 + - type: input 61 + id: browser-ver 62 + attributes: 63 + label: Browser Version 64 + description: The browser and version that you are using to access Gitea 65 + validations: 66 + required: true
+1
.github/labeler.yml
··· 22 22 - ".markdownlint.yaml" 23 23 - ".spectral.yaml" 24 24 - ".stylelintrc.yaml" 25 + - ".yamllint.yaml"
+3 -3
.github/stale.yml
··· 9 9 10 10 # Issues or Pull Requests with these labels will never be considered stale. Set to `[]` to disable 11 11 exemptLabels: 12 - - status/blocked 13 - - kind/security 12 + - status/blocked 13 + - kind/security 14 14 - lgtm/done 15 15 - reviewed/confirmed 16 16 - priority/critical ··· 27 27 28 28 # Comment to post when marking as stale. Set to `false` to disable 29 29 markComment: > 30 - This issue has been automatically marked as stale because it has not had recent activity. 30 + This issue has been automatically marked as stale because it has not had recent activity. 31 31 I am here to help clear issues left open even if solved or waiting for more insight. 32 32 This issue will be closed if no further activity occurs during the next 2 weeks. 33 33 If the issue is still valid just add a comment to keep it alive.
+8
.github/workflows/files-changed.yml
··· 17 17 value: ${{ jobs.detect.outputs.docker }} 18 18 swagger: 19 19 value: ${{ jobs.detect.outputs.swagger }} 20 + yaml: 21 + value: ${{ jobs.detect.outputs.yaml }} 20 22 21 23 jobs: 22 24 detect: ··· 30 32 templates: ${{ steps.changes.outputs.templates }} 31 33 docker: ${{ steps.changes.outputs.docker }} 32 34 swagger: ${{ steps.changes.outputs.swagger }} 35 + yaml: ${{ steps.changes.outputs.yaml }} 33 36 steps: 34 37 - uses: actions/checkout@v3 35 38 - uses: dorny/paths-filter@v2 ··· 82 85 - "package.json" 83 86 - "package-lock.json" 84 87 - ".spectral.yaml" 88 + 89 + yaml: 90 + - "**/*.yml" 91 + - "**/*.yaml" 92 + - ".yamllint.yaml"
+13
.github/workflows/pull-compliance.yml
··· 39 39 - run: make deps-py 40 40 - run: make lint-templates 41 41 42 + lint-yaml: 43 + if: needs.files-changed.outputs.yaml == 'true' 44 + needs: files-changed 45 + runs-on: ubuntu-latest 46 + steps: 47 + - uses: actions/checkout@v3 48 + - uses: actions/setup-python@v4 49 + with: 50 + python-version: "3.11" 51 + - run: pip install poetry 52 + - run: make deps-py 53 + - run: make lint-yaml 54 + 42 55 lint-swagger: 43 56 if: needs.files-changed.outputs.swagger == 'true' 44 57 needs: files-changed
+3 -3
.github/workflows/pull-db-tests.yml
··· 88 88 mysql: 89 89 image: mysql:5.7 90 90 env: 91 - MYSQL_ALLOW_EMPTY_PASSWORD: yes 91 + MYSQL_ALLOW_EMPTY_PASSWORD: true 92 92 MYSQL_DATABASE: test 93 93 ports: 94 94 - "3306:3306" ··· 160 160 mysql: 161 161 image: mysql:5.7 162 162 env: 163 - MYSQL_ALLOW_EMPTY_PASSWORD: yes 163 + MYSQL_ALLOW_EMPTY_PASSWORD: true 164 164 MYSQL_DATABASE: test 165 165 ports: 166 166 - "3306:3306" ··· 205 205 mysql8: 206 206 image: mysql:8 207 207 env: 208 - MYSQL_ALLOW_EMPTY_PASSWORD: yes 208 + MYSQL_ALLOW_EMPTY_PASSWORD: true 209 209 MYSQL_DATABASE: testgitea 210 210 ports: 211 211 - "3306:3306"
+48
.yamllint.yaml
··· 1 + extends: default 2 + 3 + rules: 4 + braces: 5 + min-spaces-inside: 0 6 + max-spaces-inside: 1 7 + min-spaces-inside-empty: 0 8 + max-spaces-inside-empty: 0 9 + 10 + brackets: 11 + min-spaces-inside: 0 12 + max-spaces-inside: 1 13 + min-spaces-inside-empty: 0 14 + max-spaces-inside-empty: 0 15 + 16 + comments: 17 + require-starting-space: true 18 + ignore-shebangs: true 19 + min-spaces-from-content: 1 20 + 21 + comments-indentation: 22 + level: error 23 + 24 + document-start: 25 + level: error 26 + present: false 27 + ignore: | 28 + /.drone.yml 29 + 30 + document-end: 31 + present: false 32 + 33 + empty-lines: 34 + max: 1 35 + 36 + indentation: 37 + spaces: 2 38 + 39 + line-length: disable 40 + 41 + truthy: 42 + allowed-values: ["true", "false", "on", "off"] 43 + 44 + ignore: | 45 + .venv 46 + node_modules 47 + /models/fixtures 48 + /models/migrations/fixtures
+5
Makefile
··· 218 218 @echo " - lint-md lint markdown files" 219 219 @echo " - lint-swagger lint swagger files" 220 220 @echo " - lint-templates lint template files" 221 + @echo " - lint-yaml lint yaml files" 221 222 @echo " - checks run various consistency checks" 222 223 @echo " - checks-frontend check frontend files" 223 224 @echo " - checks-backend check backend files" ··· 426 427 .PHONY: lint-templates 427 428 lint-templates: .venv 428 429 @poetry run djlint $(shell find templates -type f -iname '*.tmpl') 430 + 431 + .PHONY: lint-yaml 432 + lint-yaml: .venv 433 + @poetry run yamllint . 429 434 430 435 .PHONY: watch 431 436 watch:
+20 -2
poetry.lock
··· 1 - # This file is automatically @generated by Poetry 1.5.1 and should not be changed by hand. 1 + # This file is automatically @generated by Poetry 1.6.1 and should not be changed by hand. 2 2 3 3 [[package]] 4 4 name = "click" ··· 325 325 slack = ["slack-sdk"] 326 326 telegram = ["requests"] 327 327 328 + [[package]] 329 + name = "yamllint" 330 + version = "1.32.0" 331 + description = "A linter for YAML files." 332 + optional = false 333 + python-versions = ">=3.7" 334 + files = [ 335 + {file = "yamllint-1.32.0-py3-none-any.whl", hash = "sha256:d97a66e48da820829d96077d76b8dfbe6c6140f106e558dae87e81ac4e6b30b7"}, 336 + {file = "yamllint-1.32.0.tar.gz", hash = "sha256:d01dde008c65de5b235188ab3110bebc59d18e5c65fc8a58267cd211cd9df34a"}, 337 + ] 338 + 339 + [package.dependencies] 340 + pathspec = ">=0.5.3" 341 + pyyaml = "*" 342 + 343 + [package.extras] 344 + dev = ["doc8", "flake8", "flake8-import-order", "rstcheck[sphinx]", "sphinx"] 345 + 328 346 [metadata] 329 347 lock-version = "2.0" 330 348 python-versions = "^3.8" 331 - content-hash = "1b154f70c35b75d47c843959af9df0e7343f3bb579835825ca889ec9350afc41" 349 + content-hash = "4017ac7637dcc0703b37f8dc640d3e11e67e60c7b14660838135cff38ad91656"
+1
pyproject.toml
··· 9 9 10 10 [tool.poetry.group.dev.dependencies] 11 11 djlint = "1.32.1" 12 + yamllint = "^1.32.0" 12 13 13 14 [tool.djlint] 14 15 profile="golang"