aboutsummaryrefslogtreecommitdiffstats
path: root/.github
Commit message (Collapse)AuthorAgeFilesLines
* use hosted runners for nightly actions (#27485)techknowlogick2023-10-062-3/+42
| | | | | | | | I'm temporarily unable to properly evaluate actuated runners, and so I'm switching back to hosted runners until I am able to focus on that again. --------- Co-authored-by: silverwind <me@silverwind.io>
* Use minimal required version on CI and remove unnecessary services (#27429)Lunny Xiao2023-10-041-17/+3
|
* Require MySQL 8.0, PostgreSQL 12, MSSQL 2012 (#27337)silverwind2023-10-031-36/+6
| | | | | | | | | | | | | | | | | | | | | | | - MySQL 5.7 support and testing is dropped - MySQL tests now execute against 8.1, up from 5.7 and 8.0 - PostgreSQL 10 and 11 support ist dropped - PostgreSQL tests now execute against 16, up from 15 - MSSQL 2008 support is dropped - MSSQL tests now run against locked 2022 version Fixes: https://github.com/go-gitea/gitea/issues/25657 Ref: https://endoflife.date/mysql Ref: https://endoflife.date/postgresql Ref: https://endoflife.date/mssqlserver ## :warning: BREAKING :warning: Support for MySQL 5.7, PostgreSQL 10 and 11, and MSSQL 2008 is dropped. You are encouraged to upgrade to supported versions. --------- Co-authored-by: techknowlogick <techknowlogick@gitea.com>
* verify MinIO works with bitnami/minio:2023.8.31 (#27022)Earl Warren2023-10-031-3/+3
|
* Upgrading the actions/checkout@4 (#27096)puni98692023-09-167-25/+25
| | | | | | | as title ..Upgrading the actions/checkout@4 Signed-off-by: puni9869 <punitinani1@hotmail.com> Co-authored-by: silverwind <me@silverwind.io>
* Add missing deps to files-changed (#27100)silverwind2023-09-161-0/+5
| | | | | | | The `docs` and `yaml` actions categories need to run when the dependencies `markdownlin-cli` or `yamllint` change, so add those to the list of dependencies for these actions. Fixes: https://github.com/go-gitea/gitea/issues/27098
* bump all nightly builds to 16gbtechknowlogick2023-09-131-3/+3
|
* bump rootful to 16gbtechknowlogick2023-09-121-1/+1
|
* setup go in the nightly release pipelinetechknowlogick2023-09-121-0/+8
|
* Speed up nightly builds (#27045)techknowlogick2023-09-122-1/+37
| | | | | | | * Rootless/ful docker images build separately * Vendor go modules outside docker to speed up the build Thanks to Alex Ellis for these suggestions (and actuated runner build time)
* Use Actuated.dev runner for nightly buildstechknowlogick2023-09-121-2/+2
|
* Add more package registry paths to the labeler (#27032)JakobDev2023-09-121-0/+3
| | | Found this while working on #26960
* Add some more labels to labeler (#26987)silverwind2023-09-101-2/+9
| | | | | | | | - Add more automatic labels - Consistently use `**` glob for recursive directory globs. --------- Co-authored-by: techknowlogick <techknowlogick@gitea.com>
* Add `yamllint` (#26965)silverwind2023-09-078-175/+197
| | | | | | | | | 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>
* Fix yaml quoting (#26964)silverwind2023-09-071-14/+14
| | | | | Yaml [does not like](https://github.com/go-gitea/gitea/actions/runs/6115139962/job/16598147278?pr=26568) keys that start with `*` so let's quote all globs.
* Add `actions/labeler` (#26962)silverwind2023-09-072-0/+45
| | | | | Implements https://github.com/GiteaBot/gitea-backporter/issues/93 using [`actions/labeler`](https://github.com/actions/labeler). Very basic configuration, can be extended later.
* Fix filename for .spectral.yaml (#26828)silverwind2023-08-301-1/+1
| | | Mixed up yml vs. yaml previously.
* Add various missing files-changed dependencies (#26799)silverwind2023-08-301-0/+10
| | | | | | We were missing a number of config files like `.golangci.yml` in the dependencies for the pull request pipelines, which resulted in the linting not running for https://github.com/go-gitea/gitea/pull/26786 because only `.golangci.yml` had changed.
* Improve the "bug report" template and "support options" document (#26753)wxiaoguang2023-08-281-6/+3
| | | | | | | * `/help/support` is a better document than `/administration/logging-config` for bug reporting * Improve `support.en-us.md` * Move/add detailed contents into `Advanced Bug Report Tips` section * Merge `Chinese Support` section into `Support Options`
* Use docs.gitea.com instead of docs.gitea.io (#26739)Lunny Xiao2023-08-273-7/+7
|
* Update tool dependencies (#26607)silverwind2023-08-201-0/+1
| | | | | | - Updated all tool dependencies to latest versions - Add Makefile to `swagger` files because it specifies `go-swagger` version - Fix lint
* Lock go to 1.21 on CI (#26433)silverwind2023-08-105-14/+14
| | | | | | | To prevent unwanted surprises with new minor versions of go, lock the version to minor version using [semver tilde syntax](https://github.com/npm/node-semver#tilde-ranges-123-12-1). We were already getting 1.21.0 since yesterday, so use that version now as minimum.
* Refactor and enhance issue indexer to support both searching, filtering and ↵Jason Song2023-07-311-1/+7
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | paging (#26012) Fix #24662. Replace #24822 and #25708 (although it has been merged) ## Background In the past, Gitea supported issue searching with a keyword and conditions in a less efficient way. It worked by searching for issues with the keyword and obtaining limited IDs (as it is heavy to get all) on the indexer (bleve/elasticsearch/meilisearch), and then querying with conditions on the database to find a subset of the found IDs. This is why the results could be incomplete. To solve this issue, we need to store all fields that could be used as conditions in the indexer and support both keyword and additional conditions when searching with the indexer. ## Major changes - Redefine `IndexerData` to include all fields that could be used as filter conditions. - Refactor `Search(ctx context.Context, kw string, repoIDs []int64, limit, start int, state string)` to `Search(ctx context.Context, options *SearchOptions)`, so it supports more conditions now. - Change the data type stored in `issueIndexerQueue`. Use `IndexerMetadata` instead of `IndexerData` in case the data has been updated while it is in the queue. This also reduces the storage size of the queue. - Enhance searching with Bleve/Elasticsearch/Meilisearch, make them fully support `SearchOptions`. Also, update the data versions. - Keep most logic of database indexer, but remove `issues.SearchIssueIDsByKeyword` in `models` to avoid confusion where is the entry point to search issues. - Start a Meilisearch instance to test it in unit tests. - Add unit tests with almost full coverage to test Bleve/Elasticsearch/Meilisearch indexer. --------- Co-authored-by: Lunny Xiao <xiaolunwen@gmail.com>
* Docusaurus-ify (#26051)John Olheiser2023-07-261-1/+1
| | | | | | | | | | | | | | This PR cleans up the docs in a way to make them simpler to ingest by our [docs repo](https://gitea.com/gitea/gitea-docusaurus). 1. It includes all of the sed invocations our ingestion did, removing the need to do it at build time. 2. It replaces the shortcode variable replacement method with `@variable@` style, simply for easier sed invocations when required. 3. It removes unused files and moves the docs up a level as cleanup. --------- Signed-off-by: jolheiser <john.olheiser@gmail.com>
* Remove `feature` label from `feature request` issue template (#25696)Lunny Xiao2023-07-051-1/+1
| | | | We need a feature request process, so when a user submit a feature proposal, it should not be marked as feature before it has been accept.
* Update emoji set to Unicode 15 (#25595)isla w2023-06-291-0/+2
| | | | | | | | | | | Update emoji set to Unicode 15 which was added upstream here: https://github.com/github/gemoji/commit/cb5c514d472daf9b312c963987f4d7ee865c28fe <img width="854" alt="Screenshot 2023-06-29 at 11 02 56 AM" src="https://github.com/go-gitea/gitea/assets/1669571/7bfb663d-0804-4d23-a62d-f585a6783ca6"> --------- Co-authored-by: silverwind <me@silverwind.io>
* Fix `lint-swagger` action (#25593)silverwind2023-06-292-0/+18
| | | | | - Add detection for swagger changes and run `lint-swagger` on it - Remove `lint-swagger` from `lint-frontend` - Remove `lint-md` from `lint-frontend`
* Add `Makefile` to `files-changed` (#25463)silverwind2023-06-231-1/+4
| | | | | | When only `Makefile` changes, nothing currently runs. Add it to a few categories. Co-authored-by: Giteabot <teabot@gitea.io>
* Remove `deps-tools` from `backend` job (#25454)silverwind2023-06-221-1/+1
|
* add `test-frontend` back to actions (#25452)silverwind2023-06-221-0/+1
| | | | Apparently we were not running `test-frontend` on actions, this adds it back.
* Use Actions git context instead of dynamically created buildkit one (#25381)techknowlogick2023-06-201-0/+2
| | | | | | | | | | The [docker/build-push-action@v2 action](https://github.com/docker/build-push-action) by default ignores the checkout created using the actions/checkout@v2 action. When you pass a git build context to docker build, it wouldn't include the .git directory. By passing `context: .` to the build step then it'll use the Actions git context which includes the git fetch from the earlier step.
* Fetch all git data for embedding correct version in docker image (#25361)techknowlogick2023-06-191-0/+3
| | | Fix #25350
* Only run `docker-dryrun` when necessary (#25329)silverwind2023-06-182-8/+21
| | | | | | | | | `docker-dryrun` runs on almost any PR, which is a huge waste of CI resources. Run it only when the Dockerfiles change and also add a step that verifies the rootless file. --------- Co-authored-by: techknowlogick <techknowlogick@gitea.io>
* Clean up pyproject.toml and package.json, fix poetry options (#25327)silverwind2023-06-181-0/+1
| | | | | | | | | | | | - Reduce `pyproject.toml` and `package.json` to the minimal required format, removing unneeded properties. `build-system` is not needed as per [this](https://github.com/python-poetry/poetry/issues/8110#issuecomment-1595846841). - Fix `poetry.toml` options they were wrong previously. - Add dependencies of poetry files to templates `files-changed`. --------- Co-authored-by: Giteabot <teabot@gitea.io>
* build nightly docker images (#25317)techknowlogick2023-06-181-2/+30
| | | | followup of https://github.com/go-gitea/gitea/pull/25308 this time to build & push nightly docker images
* Build nightly binaries with Actions (#25308)techknowlogick2023-06-163-0/+61
| | | Co-authored-by: silverwind <me@silverwind.io>
* Add template linting via djlint (#25212)silverwind2023-06-142-1/+21
| | | | | | | | | | | | | | | | | | So I found this [linter](https://github.com/Riverside-Healthcare/djlint) which features a mode for go templates, so I gave it a try and it did find a number of valid issue, like unbalanced tags etc. It also has a number of bugs, I had to disable/workaround many issues. Given that this linter is written in python, this does add a dependency on `python` >= 3.8 and `poetry` to the development environment to be able to run this linter locally. - `e.g.` prefixes on placeholders are removed because the linter had a false-positive on `placeholder="e.g. cn=Search"` for the `attr=value` syntax and it's not ideal anyways to write `e.g.` into a placeholder because a placeholder is meant to hold a sample value. - In `templates/repo/settings/options.tmpl` I simplified the logic to not conditionally create opening tags without closing tags because this stuff confuses the linter (and possibly the reader as well).
* GitHub Actions enhancements for frontend (#25150)silverwind2023-06-144-21/+19
| | | | | - Don't run DB tests for frontend-only changes - Build frontend as part of frontend step - Build everything when actions change
* Fix setup-go actions (#25167)silverwind2023-06-092-8/+15
| | | | | | | | | | | | | | | | | | The `setup-go` actions did not all have `check-latest` which means they use some cached version of go that currently still resolves to go1.20.4, as seen in a number of recent runs that currently fail at govulncheck because of it: ```` Run actions/setup-go@v4 Setup go version spec >=1.20 Attempting to resolve the latest version from the manifest... matching >=1.20... Resolved as '1.20.4' ```` Add the [check-latest](https://github.com/actions/setup-go#check-latest-version) option which should guarantee that this cache is skipped.
* Clean up github actions (#24984)silverwind2023-05-304-51/+59
| | | | | | | - Merge the file filters into `files-changed.yml` - Remove unused yaml anchors like `&backend` - Merge the `compliance-docs` workflow into `compliance` - Add actions linting - Misc cleanups for whitespace and step names
* Fix documentation ref (#24934)Lunny Xiao2023-05-261-0/+1
| | | Fix documentation ref
* Use file filters action instead of Github's files filter (#24877)Lunny Xiao2023-05-2511-122/+92
| | | | | | | | | | | | | | | Inspired by https://github.com/go-gitea/gitea/pull/24530#issuecomment-1558815301 This PR use a file filter action to do different CI jobs according changed files types. All types are defined in `.github/file-filters.yml`. Now there are 4 types, `docs`, `backend`, `frontend` and `build`. Then if a PR only changed docs files, those CI jobs which passed the conditions will run, and other types are also like this. --------- Co-authored-by: silverwind <me@silverwind.io>
* Remove publish docs CI workflow (#24889)techknowlogick2023-05-231-29/+0
| | | | Now that the redirect to docs.gitea.com is in place this is no longer needed.
* replace `drone exec` to `act_runner exec` in test README.md (#24791)a10121127962023-05-181-5/+5
|
* Ignore build for docs only (#24761)Lunny Xiao2023-05-171-0/+30
| | | Fix https://github.com/go-gitea/gitea/pull/24530#issuecomment-1550227919
* Don't run build and test if only docs changed (#24530)Lunny Xiao2023-05-1611-5/+101
| | | Co-authored-by: techknowlogick <techknowlogick@gitea.io>
* Update cron-translations.yml (#24708)Lunny Xiao2023-05-141-0/+1
| | | Fix cron translations push failure
* fix minio storage iterator path (#24691)FuXiaoHei2023-05-131-0/+7
| | | | | | | | | | | | | | | | | | | | | | | | | | minio storage iterator shows different behavior with local fs iterator. in local fs storage: ``` go s.IterateObjects("prefix", func(path,obj) println(path) // show "prefix/xxx.file" }) ``` in minio storage: ```go s.IterateObjects("prefix", func(path,obj) println(path) // show "xxx.file" }) ``` I think local fs is correct, minio use wrong `basePath` to trim storage path prefix. --------- Co-authored-by: Giteabot <teabot@gitea.io>
* GitHub Actions cleanups (#24620)silverwind2023-05-1112-286/+171
| | | | | | | | | | - Remove actions name where command is descriptive enough - Use kebab-case instead of snake-case for step names - Use shorter job names because to make PR checks more readable - Remove duplicate `checks-backend` --------- Co-authored-by: Yarden Shoham <git@yardenshoham.com>
* Kd/fix redis unit test (#24650)Kyle D2023-05-111-0/+10
| | | | | | | | | Replaces #24641 Currently, unit tests fail when run locally (unless users have minio instance running). This PR only requires redis unit tests if in CI. - Only run redis unit tests when `CI` env variable is set - Add minio as a service in unit tests actions
generated by cgit v1.2.3 (git 2.39.1) at 2025-01-11 10:45:32 +0000