b5d21c0adf
We can not have the `frontend` target depend on golang because of they way drone is set up. Move the `go-licenses` generation back into `tidy` where it will now also be checked for consistency during `tidy-check`. (I assume all `main` branch builds should currently fail [like this](https://drone.gitea.io/go-gitea/gitea/60244/1/11)). The reasony why it shouldn't be treated the same as for example `go generate` is because output files are checked in. tidy is imho the optimal target to run this after. Co-authored-by: Lunny Xiao <xiaolunwen@gmail.com> |
||
|---|---|---|
| .. | ||
| codeformat | ||
| code-batch-process.go | ||
| generate-bindata.go | ||
| generate-emoji.go | ||
| generate-gitignores.go | ||
| generate-go-licenses.go | ||
| generate-images.js | ||
| generate-licenses.go | ||
| generate-svg.js | ||
| gocovmerge.go | ||
| test-env-check.sh | ||
| test-env-prepare.sh | ||
| update-locales.sh | ||