Shiloh/githaven
Shiloh/githaven
1
0
Fork 1
Code Issues Pull Requests Actions 1 Packages Projects Releases Wiki Activity
d3cdef88ad
githaven/.github/workflows/pull-compliance.yml

207 lines
6.1 KiB
YAML
Raw Normal View History

GitHub Actions cleanups (#24620) - 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>
2023-05-12 01:21:28 +00:00
name: compliance
Use Actions for DB & E2E tests (#24494) following https://github.com/go-gitea/gitea/pull/24314 and https://github.com/go-gitea/gitea/pull/24434, this PR moves drone cron pipelines to (GitHub) Actions. As these are mostly compatible with Gitea Actions, when we start to dogfood, these will already be migrated. --------- Co-authored-by: silverwind <me@silverwind.io>
2023-05-04 02:04:02 +00:00
Don't run build and test if only docs changed (#24530) Co-authored-by: techknowlogick <techknowlogick@gitea.io>
2023-05-16 02:53:18 +00:00
on:
pull_request:
Use Actions for DB & E2E tests (#24494) following https://github.com/go-gitea/gitea/pull/24314 and https://github.com/go-gitea/gitea/pull/24434, this PR moves drone cron pipelines to (GitHub) Actions. As these are mostly compatible with Gitea Actions, when we start to dogfood, these will already be migrated. --------- Co-authored-by: silverwind <me@silverwind.io>
2023-05-04 02:04:02 +00:00
Upgrade to Node 20 on CI, enable actions cancellation (#24524) - Upgrade node, the [snap](https://github.com/go-gitea/gitea/blob/7abe958f5b507efa676fb3b2e27d30517f6d1908/snap/snapcraft.yaml#L47) is excluded from this because [there is no Node 20 snap yet](https://snapcraft.io/node). - Add actions build cancellation based on [this](https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#example-using-a-fallback-value). --------- Co-authored-by: techknowlogick <techknowlogick@gitea.io>
2023-05-04 22:21:48 +00:00
concurrency:
group: ${{ github.workflow }}-${{ github.head_ref || github.run_id }}
cancel-in-progress: true
Use Actions for DB & E2E tests (#24494) following https://github.com/go-gitea/gitea/pull/24314 and https://github.com/go-gitea/gitea/pull/24434, this PR moves drone cron pipelines to (GitHub) Actions. As these are mostly compatible with Gitea Actions, when we start to dogfood, these will already be migrated. --------- Co-authored-by: silverwind <me@silverwind.io>
2023-05-04 02:04:02 +00:00
jobs:
Use file filters action instead of Github's files filter (#24877) 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>
2023-05-25 01:33:31 +00:00
files-changed:
uses: ./.github/workflows/files-changed.yml
GitHub Actions cleanups (#24620) - 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>
2023-05-12 01:21:28 +00:00
lint-backend:
GitHub Actions enhancements for frontend (#25150) - Don't run DB tests for frontend-only changes - Build frontend as part of frontend step - Build everything when actions change
2023-06-14 15:30:37 +00:00
if: needs.files-changed.outputs.backend == 'true' || needs.files-changed.outputs.actions == 'true'
Use file filters action instead of Github's files filter (#24877) 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>
2023-05-25 01:33:31 +00:00
needs: files-changed
Use Actions for DB & E2E tests (#24494) following https://github.com/go-gitea/gitea/pull/24314 and https://github.com/go-gitea/gitea/pull/24434, this PR moves drone cron pipelines to (GitHub) Actions. As these are mostly compatible with Gitea Actions, when we start to dogfood, these will already be migrated. --------- Co-authored-by: silverwind <me@silverwind.io>
2023-05-04 02:04:02 +00:00
runs-on: ubuntu-latest
steps:
Upgrading the actions/checkout@4 (#27096) as title ..Upgrading the actions/checkout@4 Signed-off-by: puni9869 <punitinani1@hotmail.com> Co-authored-by: silverwind <me@silverwind.io>
2023-09-16 15:06:27 +00:00
- uses: actions/checkout@v4
feat: bump `dessant/lock-threads` and `actions/setup-go` to use nodejs20 runtime (#28565) Update more actions to use nodejs20 runtime and also update the docs for checkout action usage. similar to: - #27836 - #27096 --------- Signed-off-by: Rui Chen <rui@chenrui.dev>
2023-12-21 05:31:04 +00:00
- uses: actions/setup-go@v5
Use Actions for DB & E2E tests (#24494) following https://github.com/go-gitea/gitea/pull/24314 and https://github.com/go-gitea/gitea/pull/24434, this PR moves drone cron pipelines to (GitHub) Actions. As these are mostly compatible with Gitea Actions, when we start to dogfood, these will already be migrated. --------- Co-authored-by: silverwind <me@silverwind.io>
2023-05-04 02:04:02 +00:00
with:
actions/setup-go use go-version-file (#27651) These changes will allow not to specify the version of go in every pipeline.
2023-10-17 10:24:54 +00:00
go-version-file: go.mod
Check latest version on CI (#24556)
2023-05-06 07:43:56 +00:00
check-latest: true
GitHub Actions cleanups (#24620) - 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>
2023-05-12 01:21:28 +00:00
- run: make deps-backend deps-tools
- run: make lint-backend
Use Actions for DB & E2E tests (#24494) following https://github.com/go-gitea/gitea/pull/24314 and https://github.com/go-gitea/gitea/pull/24434, this PR moves drone cron pipelines to (GitHub) Actions. As these are mostly compatible with Gitea Actions, when we start to dogfood, these will already be migrated. --------- Co-authored-by: silverwind <me@silverwind.io>
2023-05-04 02:04:02 +00:00
env:
TAGS: bindata sqlite sqlite_unlock_notify
Clean up github actions (#24984) - 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
2023-05-30 05:31:00 +00:00
Add template linting via djlint (#25212) 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).
2023-06-14 18:17:58 +00:00
lint-templates:
if: needs.files-changed.outputs.templates == 'true'
needs: files-changed
runs-on: ubuntu-latest
steps:
Upgrading the actions/checkout@4 (#27096) as title ..Upgrading the actions/checkout@4 Signed-off-by: puni9869 <punitinani1@hotmail.com> Co-authored-by: silverwind <me@silverwind.io>
2023-09-16 15:06:27 +00:00
- uses: actions/checkout@v4
Update js and py dependencies, bump python (#29561) - Update js and py dependencies excluding `@mcaptcha/vanilla-glue`, `eslint-plugin-array-func` - Update stylelint config - Require python 3.10 and use 3.12 on CI, bump setup-python as well - Tested markdown toolbar, charts, clipboard, swagger ui, vue
2024-03-03 16:23:14 +00:00
- uses: actions/setup-python@v5
Add template linting via djlint (#25212) 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).
2023-06-14 18:17:58 +00:00
with:
Update js and py dependencies, bump python (#29561) - Update js and py dependencies excluding `@mcaptcha/vanilla-glue`, `eslint-plugin-array-func` - Update stylelint config - Require python 3.10 and use 3.12 on CI, bump setup-python as well - Tested markdown toolbar, charts, clipboard, swagger ui, vue
2024-03-03 16:23:14 +00:00
python-version: "3.12"
Add svg linter and fix incorrect svgs (#30086) Fixes https://github.com/go-gitea/gitea/issues/30082. Adds a new linter that searches for non-existant SVG images in templates. Output before the fix was: ``` $ make lint-templates SVG "octicon-warning" not found, used in templates/devtest/flex-list.tmpl SVG "octicon-warning" not found, used in templates/devtest/flex-list.tmpl SVG "octicon-markup" not found, used in templates/repo/diff/comment_form.tmpl make: *** [Makefile:438: lint-templates] Error 1 ``` <img width="306" alt="Screenshot 2024-03-25 at 23 31 05" src="https://github.com/go-gitea/gitea/assets/115237/1052d1a9-bfec-4d5a-9cae-f895f78f7c93">
2024-03-26 11:19:15 +00:00
- uses: actions/setup-node@v4
with:
node-version: 20
Enable npm cache on `setup-node` action (#30577) Enable npm dependency cache in [setup-node](https://github.com/actions/setup-node). This should work reliably and across branches as well.
2024-04-19 03:29:08 +00:00
cache: npm
cache-dependency-path: package-lock.json
Add template linting via djlint (#25212) 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).
2023-06-14 18:17:58 +00:00
- run: pip install poetry
- run: make deps-py
Add svg linter and fix incorrect svgs (#30086) Fixes https://github.com/go-gitea/gitea/issues/30082. Adds a new linter that searches for non-existant SVG images in templates. Output before the fix was: ``` $ make lint-templates SVG "octicon-warning" not found, used in templates/devtest/flex-list.tmpl SVG "octicon-warning" not found, used in templates/devtest/flex-list.tmpl SVG "octicon-markup" not found, used in templates/repo/diff/comment_form.tmpl make: *** [Makefile:438: lint-templates] Error 1 ``` <img width="306" alt="Screenshot 2024-03-25 at 23 31 05" src="https://github.com/go-gitea/gitea/assets/115237/1052d1a9-bfec-4d5a-9cae-f895f78f7c93">
2024-03-26 11:19:15 +00:00
- run: make deps-frontend
Add template linting via djlint (#25212) 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).
2023-06-14 18:17:58 +00:00
- run: make lint-templates
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>
2023-09-08 02:24:06 +00:00
lint-yaml:
if: needs.files-changed.outputs.yaml == 'true'
needs: files-changed
runs-on: ubuntu-latest
steps:
Upgrading the actions/checkout@4 (#27096) as title ..Upgrading the actions/checkout@4 Signed-off-by: puni9869 <punitinani1@hotmail.com> Co-authored-by: silverwind <me@silverwind.io>
2023-09-16 15:06:27 +00:00
- uses: actions/checkout@v4
Update js and py dependencies, bump python (#29561) - Update js and py dependencies excluding `@mcaptcha/vanilla-glue`, `eslint-plugin-array-func` - Update stylelint config - Require python 3.10 and use 3.12 on CI, bump setup-python as well - Tested markdown toolbar, charts, clipboard, swagger ui, vue
2024-03-03 16:23:14 +00:00
- uses: actions/setup-python@v5
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>
2023-09-08 02:24:06 +00:00
with:
Update js and py dependencies, bump python (#29561) - Update js and py dependencies excluding `@mcaptcha/vanilla-glue`, `eslint-plugin-array-func` - Update stylelint config - Require python 3.10 and use 3.12 on CI, bump setup-python as well - Tested markdown toolbar, charts, clipboard, swagger ui, vue
2024-03-03 16:23:14 +00:00
python-version: "3.12"
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>
2023-09-08 02:24:06 +00:00
- run: pip install poetry
- run: make deps-py
- run: make lint-yaml
Fix `lint-swagger` action (#25593) - Add detection for swagger changes and run `lint-swagger` on it - Remove `lint-swagger` from `lint-frontend` - Remove `lint-md` from `lint-frontend`
2023-06-29 14:37:41 +00:00
lint-swagger:
if: needs.files-changed.outputs.swagger == 'true'
needs: files-changed
runs-on: ubuntu-latest
steps:
Upgrading the actions/checkout@4 (#27096) as title ..Upgrading the actions/checkout@4 Signed-off-by: puni9869 <punitinani1@hotmail.com> Co-authored-by: silverwind <me@silverwind.io>
2023-09-16 15:06:27 +00:00
- uses: actions/checkout@v4
Bump workflows in github actions (#27836) All major version upgrades are related to using Node v20 as default runtime
2023-10-30 07:56:43 +00:00
- uses: actions/setup-node@v4
Fix `lint-swagger` action (#25593) - Add detection for swagger changes and run `lint-swagger` on it - Remove `lint-swagger` from `lint-frontend` - Remove `lint-md` from `lint-frontend`
2023-06-29 14:37:41 +00:00
with:
node-version: 20
Enable npm cache on `setup-node` action (#30577) Enable npm dependency cache in [setup-node](https://github.com/actions/setup-node). This should work reliably and across branches as well.
2024-04-19 03:29:08 +00:00
cache: npm
cache-dependency-path: package-lock.json
Fix `lint-swagger` action (#25593) - Add detection for swagger changes and run `lint-swagger` on it - Remove `lint-swagger` from `lint-frontend` - Remove `lint-md` from `lint-frontend`
2023-06-29 14:37:41 +00:00
- run: make deps-frontend
- run: make lint-swagger
Rework spellchecking, add `lint-spell` (#29106) - Use maintained fork https://github.com/golangci/misspell - Rename `mispell-check` to `lint-spell`, add `lint-spell-fix` - Run `lint-spell` in separate actions step - Lint more files, fix discovered issues - Remove inaccurate and outdated info in docs (we do not need GOPATH for tools anymore) Maybe later we can add more spellchecking tools, but I have not found any good ones yet.
2024-02-09 03:59:39 +00:00
lint-spell:
if: needs.files-changed.outputs.backend == 'true' || needs.files-changed.outputs.frontend == 'true' || needs.files-changed.outputs.actions == 'true' || needs.files-changed.outputs.docs == 'true' || needs.files-changed.outputs.templates == 'true'
needs: files-changed
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- uses: actions/setup-go@v5
with:
go-version-file: go.mod
check-latest: true
- run: make lint-spell
GitHub Actions cleanups (#24620) - 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>
2023-05-12 01:21:28 +00:00
lint-go-windows:
GitHub Actions enhancements for frontend (#25150) - Don't run DB tests for frontend-only changes - Build frontend as part of frontend step - Build everything when actions change
2023-06-14 15:30:37 +00:00
if: needs.files-changed.outputs.backend == 'true' || needs.files-changed.outputs.actions == 'true'
Use file filters action instead of Github's files filter (#24877) 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>
2023-05-25 01:33:31 +00:00
needs: files-changed
Use Actions for DB & E2E tests (#24494) following https://github.com/go-gitea/gitea/pull/24314 and https://github.com/go-gitea/gitea/pull/24434, this PR moves drone cron pipelines to (GitHub) Actions. As these are mostly compatible with Gitea Actions, when we start to dogfood, these will already be migrated. --------- Co-authored-by: silverwind <me@silverwind.io>
2023-05-04 02:04:02 +00:00
runs-on: ubuntu-latest
steps:
Upgrading the actions/checkout@4 (#27096) as title ..Upgrading the actions/checkout@4 Signed-off-by: puni9869 <punitinani1@hotmail.com> Co-authored-by: silverwind <me@silverwind.io>
2023-09-16 15:06:27 +00:00
- uses: actions/checkout@v4
feat: bump `dessant/lock-threads` and `actions/setup-go` to use nodejs20 runtime (#28565) Update more actions to use nodejs20 runtime and also update the docs for checkout action usage. similar to: - #27836 - #27096 --------- Signed-off-by: Rui Chen <rui@chenrui.dev>
2023-12-21 05:31:04 +00:00
- uses: actions/setup-go@v5
Use Actions for DB & E2E tests (#24494) following https://github.com/go-gitea/gitea/pull/24314 and https://github.com/go-gitea/gitea/pull/24434, this PR moves drone cron pipelines to (GitHub) Actions. As these are mostly compatible with Gitea Actions, when we start to dogfood, these will already be migrated. --------- Co-authored-by: silverwind <me@silverwind.io>
2023-05-04 02:04:02 +00:00
with:
actions/setup-go use go-version-file (#27651) These changes will allow not to specify the version of go in every pipeline.
2023-10-17 10:24:54 +00:00
go-version-file: go.mod
Check latest version on CI (#24556)
2023-05-06 07:43:56 +00:00
check-latest: true
GitHub Actions cleanups (#24620) - 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>
2023-05-12 01:21:28 +00:00
- run: make deps-backend deps-tools
- run: make lint-go-windows lint-go-vet
Use Actions for DB & E2E tests (#24494) following https://github.com/go-gitea/gitea/pull/24314 and https://github.com/go-gitea/gitea/pull/24434, this PR moves drone cron pipelines to (GitHub) Actions. As these are mostly compatible with Gitea Actions, when we start to dogfood, these will already be migrated. --------- Co-authored-by: silverwind <me@silverwind.io>
2023-05-04 02:04:02 +00:00
env:
TAGS: bindata sqlite sqlite_unlock_notify
GOOS: windows
GOARCH: amd64
Clean up github actions (#24984) - 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
2023-05-30 05:31:00 +00:00
GitHub Actions cleanups (#24620) - 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>
2023-05-12 01:21:28 +00:00
lint-go-gogit:
GitHub Actions enhancements for frontend (#25150) - Don't run DB tests for frontend-only changes - Build frontend as part of frontend step - Build everything when actions change
2023-06-14 15:30:37 +00:00
if: needs.files-changed.outputs.backend == 'true' || needs.files-changed.outputs.actions == 'true'
Use file filters action instead of Github's files filter (#24877) 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>
2023-05-25 01:33:31 +00:00
needs: files-changed
Use Actions for DB & E2E tests (#24494) following https://github.com/go-gitea/gitea/pull/24314 and https://github.com/go-gitea/gitea/pull/24434, this PR moves drone cron pipelines to (GitHub) Actions. As these are mostly compatible with Gitea Actions, when we start to dogfood, these will already be migrated. --------- Co-authored-by: silverwind <me@silverwind.io>
2023-05-04 02:04:02 +00:00
runs-on: ubuntu-latest
steps:
Upgrading the actions/checkout@4 (#27096) as title ..Upgrading the actions/checkout@4 Signed-off-by: puni9869 <punitinani1@hotmail.com> Co-authored-by: silverwind <me@silverwind.io>
2023-09-16 15:06:27 +00:00
- uses: actions/checkout@v4
feat: bump `dessant/lock-threads` and `actions/setup-go` to use nodejs20 runtime (#28565) Update more actions to use nodejs20 runtime and also update the docs for checkout action usage. similar to: - #27836 - #27096 --------- Signed-off-by: Rui Chen <rui@chenrui.dev>
2023-12-21 05:31:04 +00:00
- uses: actions/setup-go@v5
Use Actions for DB & E2E tests (#24494) following https://github.com/go-gitea/gitea/pull/24314 and https://github.com/go-gitea/gitea/pull/24434, this PR moves drone cron pipelines to (GitHub) Actions. As these are mostly compatible with Gitea Actions, when we start to dogfood, these will already be migrated. --------- Co-authored-by: silverwind <me@silverwind.io>
2023-05-04 02:04:02 +00:00
with:
actions/setup-go use go-version-file (#27651) These changes will allow not to specify the version of go in every pipeline.
2023-10-17 10:24:54 +00:00
go-version-file: go.mod
Check latest version on CI (#24556)
2023-05-06 07:43:56 +00:00
check-latest: true
GitHub Actions cleanups (#24620) - 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>
2023-05-12 01:21:28 +00:00
- run: make deps-backend deps-tools
- run: make lint-go
Use Actions for DB & E2E tests (#24494) following https://github.com/go-gitea/gitea/pull/24314 and https://github.com/go-gitea/gitea/pull/24434, this PR moves drone cron pipelines to (GitHub) Actions. As these are mostly compatible with Gitea Actions, when we start to dogfood, these will already be migrated. --------- Co-authored-by: silverwind <me@silverwind.io>
2023-05-04 02:04:02 +00:00
env:
TAGS: bindata gogit sqlite sqlite_unlock_notify
Clean up github actions (#24984) - 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
2023-05-30 05:31:00 +00:00
GitHub Actions cleanups (#24620) - 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>
2023-05-12 01:21:28 +00:00
checks-backend:
GitHub Actions enhancements for frontend (#25150) - Don't run DB tests for frontend-only changes - Build frontend as part of frontend step - Build everything when actions change
2023-06-14 15:30:37 +00:00
if: needs.files-changed.outputs.backend == 'true' || needs.files-changed.outputs.actions == 'true'
Use file filters action instead of Github's files filter (#24877) 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>
2023-05-25 01:33:31 +00:00
needs: files-changed
Use Actions for DB & E2E tests (#24494) following https://github.com/go-gitea/gitea/pull/24314 and https://github.com/go-gitea/gitea/pull/24434, this PR moves drone cron pipelines to (GitHub) Actions. As these are mostly compatible with Gitea Actions, when we start to dogfood, these will already be migrated. --------- Co-authored-by: silverwind <me@silverwind.io>
2023-05-04 02:04:02 +00:00
runs-on: ubuntu-latest
steps:
Upgrading the actions/checkout@4 (#27096) as title ..Upgrading the actions/checkout@4 Signed-off-by: puni9869 <punitinani1@hotmail.com> Co-authored-by: silverwind <me@silverwind.io>
2023-09-16 15:06:27 +00:00
- uses: actions/checkout@v4
feat: bump `dessant/lock-threads` and `actions/setup-go` to use nodejs20 runtime (#28565) Update more actions to use nodejs20 runtime and also update the docs for checkout action usage. similar to: - #27836 - #27096 --------- Signed-off-by: Rui Chen <rui@chenrui.dev>
2023-12-21 05:31:04 +00:00
- uses: actions/setup-go@v5
Use Actions for DB & E2E tests (#24494) following https://github.com/go-gitea/gitea/pull/24314 and https://github.com/go-gitea/gitea/pull/24434, this PR moves drone cron pipelines to (GitHub) Actions. As these are mostly compatible with Gitea Actions, when we start to dogfood, these will already be migrated. --------- Co-authored-by: silverwind <me@silverwind.io>
2023-05-04 02:04:02 +00:00
with:
actions/setup-go use go-version-file (#27651) These changes will allow not to specify the version of go in every pipeline.
2023-10-17 10:24:54 +00:00
go-version-file: go.mod
Check latest version on CI (#24556)
2023-05-06 07:43:56 +00:00
check-latest: true
GitHub Actions cleanups (#24620) - 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>
2023-05-12 01:21:28 +00:00
- run: make deps-backend deps-tools
- run: make --always-make checks-backend # ensure the "go-licenses" make target runs
Clean up github actions (#24984) - 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
2023-05-30 05:31:00 +00:00
Use Actions for DB & E2E tests (#24494) following https://github.com/go-gitea/gitea/pull/24314 and https://github.com/go-gitea/gitea/pull/24434, this PR moves drone cron pipelines to (GitHub) Actions. As these are mostly compatible with Gitea Actions, when we start to dogfood, these will already be migrated. --------- Co-authored-by: silverwind <me@silverwind.io>
2023-05-04 02:04:02 +00:00
frontend:
GitHub Actions enhancements for frontend (#25150) - Don't run DB tests for frontend-only changes - Build frontend as part of frontend step - Build everything when actions change
2023-06-14 15:30:37 +00:00
if: needs.files-changed.outputs.frontend == 'true' || needs.files-changed.outputs.actions == 'true'
Use file filters action instead of Github's files filter (#24877) 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>
2023-05-25 01:33:31 +00:00
needs: files-changed
Use Actions for DB & E2E tests (#24494) following https://github.com/go-gitea/gitea/pull/24314 and https://github.com/go-gitea/gitea/pull/24434, this PR moves drone cron pipelines to (GitHub) Actions. As these are mostly compatible with Gitea Actions, when we start to dogfood, these will already be migrated. --------- Co-authored-by: silverwind <me@silverwind.io>
2023-05-04 02:04:02 +00:00
runs-on: ubuntu-latest
steps:
Upgrading the actions/checkout@4 (#27096) as title ..Upgrading the actions/checkout@4 Signed-off-by: puni9869 <punitinani1@hotmail.com> Co-authored-by: silverwind <me@silverwind.io>
2023-09-16 15:06:27 +00:00
- uses: actions/checkout@v4
Bump workflows in github actions (#27836) All major version upgrades are related to using Node v20 as default runtime
2023-10-30 07:56:43 +00:00
- uses: actions/setup-node@v4
Use Actions for DB & E2E tests (#24494) following https://github.com/go-gitea/gitea/pull/24314 and https://github.com/go-gitea/gitea/pull/24434, this PR moves drone cron pipelines to (GitHub) Actions. As these are mostly compatible with Gitea Actions, when we start to dogfood, these will already be migrated. --------- Co-authored-by: silverwind <me@silverwind.io>
2023-05-04 02:04:02 +00:00
with:
Upgrade to Node 20 on CI, enable actions cancellation (#24524) - Upgrade node, the [snap](https://github.com/go-gitea/gitea/blob/7abe958f5b507efa676fb3b2e27d30517f6d1908/snap/snapcraft.yaml#L47) is excluded from this because [there is no Node 20 snap yet](https://snapcraft.io/node). - Add actions build cancellation based on [this](https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#example-using-a-fallback-value). --------- Co-authored-by: techknowlogick <techknowlogick@gitea.io>
2023-05-04 22:21:48 +00:00
node-version: 20
Enable npm cache on `setup-node` action (#30577) Enable npm dependency cache in [setup-node](https://github.com/actions/setup-node). This should work reliably and across branches as well.
2024-04-19 03:29:08 +00:00
cache: npm
cache-dependency-path: package-lock.json
GitHub Actions cleanups (#24620) - 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>
2023-05-12 01:21:28 +00:00
- run: make deps-frontend
- run: make lint-frontend
- run: make checks-frontend
add `test-frontend` back to actions (#25452) Apparently we were not running `test-frontend` on actions, this adds it back.
2023-06-22 21:37:50 +00:00
- run: make test-frontend
GitHub Actions enhancements for frontend (#25150) - Don't run DB tests for frontend-only changes - Build frontend as part of frontend step - Build everything when actions change
2023-06-14 15:30:37 +00:00
- run: make frontend
Clean up github actions (#24984) - 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
2023-05-30 05:31:00 +00:00
Use Actions for DB & E2E tests (#24494) following https://github.com/go-gitea/gitea/pull/24314 and https://github.com/go-gitea/gitea/pull/24434, this PR moves drone cron pipelines to (GitHub) Actions. As these are mostly compatible with Gitea Actions, when we start to dogfood, these will already be migrated. --------- Co-authored-by: silverwind <me@silverwind.io>
2023-05-04 02:04:02 +00:00
backend:
GitHub Actions enhancements for frontend (#25150) - Don't run DB tests for frontend-only changes - Build frontend as part of frontend step - Build everything when actions change
2023-06-14 15:30:37 +00:00
if: needs.files-changed.outputs.backend == 'true' || needs.files-changed.outputs.actions == 'true'
Use file filters action instead of Github's files filter (#24877) 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>
2023-05-25 01:33:31 +00:00
needs: files-changed
Use Actions for DB & E2E tests (#24494) following https://github.com/go-gitea/gitea/pull/24314 and https://github.com/go-gitea/gitea/pull/24434, this PR moves drone cron pipelines to (GitHub) Actions. As these are mostly compatible with Gitea Actions, when we start to dogfood, these will already be migrated. --------- Co-authored-by: silverwind <me@silverwind.io>
2023-05-04 02:04:02 +00:00
runs-on: ubuntu-latest
steps:
Upgrading the actions/checkout@4 (#27096) as title ..Upgrading the actions/checkout@4 Signed-off-by: puni9869 <punitinani1@hotmail.com> Co-authored-by: silverwind <me@silverwind.io>
2023-09-16 15:06:27 +00:00
- uses: actions/checkout@v4
feat: bump `dessant/lock-threads` and `actions/setup-go` to use nodejs20 runtime (#28565) Update more actions to use nodejs20 runtime and also update the docs for checkout action usage. similar to: - #27836 - #27096 --------- Signed-off-by: Rui Chen <rui@chenrui.dev>
2023-12-21 05:31:04 +00:00
- uses: actions/setup-go@v5
Use Actions for DB & E2E tests (#24494) following https://github.com/go-gitea/gitea/pull/24314 and https://github.com/go-gitea/gitea/pull/24434, this PR moves drone cron pipelines to (GitHub) Actions. As these are mostly compatible with Gitea Actions, when we start to dogfood, these will already be migrated. --------- Co-authored-by: silverwind <me@silverwind.io>
2023-05-04 02:04:02 +00:00
with:
actions/setup-go use go-version-file (#27651) These changes will allow not to specify the version of go in every pipeline.
2023-10-17 10:24:54 +00:00
go-version-file: go.mod
Check latest version on CI (#24556)
2023-05-06 07:43:56 +00:00
check-latest: true
GitHub Actions enhancements for frontend (#25150) - Don't run DB tests for frontend-only changes - Build frontend as part of frontend step - Build everything when actions change
2023-06-14 15:30:37 +00:00
# no frontend build here as backend should be able to build
# even without any frontend files
Remove `deps-tools` from `backend` job (#25454)
2023-06-22 23:24:55 +00:00
- run: make deps-backend
GitHub Actions cleanups (#24620) - 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>
2023-05-12 01:21:28 +00:00
- run: go build -o gitea_no_gcc # test if build succeeds without the sqlite tag
Use Actions for DB & E2E tests (#24494) following https://github.com/go-gitea/gitea/pull/24314 and https://github.com/go-gitea/gitea/pull/24434, this PR moves drone cron pipelines to (GitHub) Actions. As these are mostly compatible with Gitea Actions, when we start to dogfood, these will already be migrated. --------- Co-authored-by: silverwind <me@silverwind.io>
2023-05-04 02:04:02 +00:00
- name: build-backend-arm64
run: make backend # test cross compile
env:
GOOS: linux
GOARCH: arm64
TAGS: bindata gogit
- name: build-backend-windows
run: go build -o gitea_windows
env:
GOOS: windows
GOARCH: amd64
TAGS: bindata gogit
- name: build-backend-386
run: go build -o gitea_linux_386 # test if compatible with 32 bit
env:
GOOS: linux
GOARCH: 386
Clean up github actions (#24984) - 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
2023-05-30 05:31:00 +00:00
docs:
GitHub Actions enhancements for frontend (#25150) - Don't run DB tests for frontend-only changes - Build frontend as part of frontend step - Build everything when actions change
2023-06-14 15:30:37 +00:00
if: needs.files-changed.outputs.docs == 'true' || needs.files-changed.outputs.actions == 'true'
Clean up github actions (#24984) - 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
2023-05-30 05:31:00 +00:00
needs: files-changed
runs-on: ubuntu-latest
steps:
Upgrading the actions/checkout@4 (#27096) as title ..Upgrading the actions/checkout@4 Signed-off-by: puni9869 <punitinani1@hotmail.com> Co-authored-by: silverwind <me@silverwind.io>
2023-09-16 15:06:27 +00:00
- uses: actions/checkout@v4
Bump workflows in github actions (#27836) All major version upgrades are related to using Node v20 as default runtime
2023-10-30 07:56:43 +00:00
- uses: actions/setup-node@v4
Clean up github actions (#24984) - 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
2023-05-30 05:31:00 +00:00
with:
node-version: 20
Enable npm cache on `setup-node` action (#30577) Enable npm dependency cache in [setup-node](https://github.com/actions/setup-node). This should work reliably and across branches as well.
2024-04-19 03:29:08 +00:00
cache: npm
cache-dependency-path: package-lock.json
Clean up github actions (#24984) - 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
2023-05-30 05:31:00 +00:00
- run: make deps-frontend
- run: make lint-md
Docusaurus-ify (#26051) 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>
2023-07-26 04:53:13 +00:00
- run: make docs
Clean up github actions (#24984) - 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
2023-05-30 05:31:00 +00:00
actions:
GitHub Actions enhancements for frontend (#25150) - Don't run DB tests for frontend-only changes - Build frontend as part of frontend step - Build everything when actions change
2023-06-14 15:30:37 +00:00
if: needs.files-changed.outputs.actions == 'true' || needs.files-changed.outputs.actions == 'true'
Clean up github actions (#24984) - 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
2023-05-30 05:31:00 +00:00
needs: files-changed
runs-on: ubuntu-latest
steps:
Upgrading the actions/checkout@4 (#27096) as title ..Upgrading the actions/checkout@4 Signed-off-by: puni9869 <punitinani1@hotmail.com> Co-authored-by: silverwind <me@silverwind.io>
2023-09-16 15:06:27 +00:00
- uses: actions/checkout@v4
feat: bump `dessant/lock-threads` and `actions/setup-go` to use nodejs20 runtime (#28565) Update more actions to use nodejs20 runtime and also update the docs for checkout action usage. similar to: - #27836 - #27096 --------- Signed-off-by: Rui Chen <rui@chenrui.dev>
2023-12-21 05:31:04 +00:00
- uses: actions/setup-go@v5
actions/setup-go use go-version-file (#27651) These changes will allow not to specify the version of go in every pipeline.
2023-10-17 10:24:54 +00:00
with:
go-version-file: go.mod
check-latest: true
Clean up github actions (#24984) - 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
2023-05-30 05:31:00 +00:00
- run: make lint-actions
Reference in New Issue Copy Permalink