forgejo/build
silverwind b5d21c0adf
Generate go-licenses during tidy again (#21108)
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>
2022-09-09 11:33:01 -04:00
..
codeformat
code-batch-process.go Kd/ci playwright go test (#20123) 2022-09-02 15:18:23 -04:00
generate-bindata.go Remove legacy +build: constraint (#19582) 2022-05-02 23:22:45 +08:00
generate-emoji.go Go 1.19 format (#20758) 2022-08-30 21:15:45 -05:00
generate-gitignores.go Remove legacy +build: constraint (#19582) 2022-05-02 23:22:45 +08:00
generate-go-licenses.go Generate go-licenses during tidy again (#21108) 2022-09-09 11:33:01 -04:00
generate-images.js Modernize JS build scripts (#19824) 2022-06-06 11:27:25 +08:00
generate-licenses.go Remove deprecated licenses (#20222) 2022-08-22 00:33:01 -04:00
generate-svg.js Modernize JS build scripts (#19824) 2022-06-06 11:27:25 +08:00
gocovmerge.go Remove legacy +build: constraint (#19582) 2022-05-02 23:22:45 +08:00
test-env-check.sh
test-env-prepare.sh
update-locales.sh