Mirrors/gitea
0
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2024-12-22 12:15:34 +01:00
Code Issues Activity
cc5ff98e0d
gitea/.github/workflows/cron-licenses.yml

30 lines
834 B
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 03:21:28 +02:00
name: cron-licenses
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 04:04:02 +02:00
switch to use Actions from drone for cron (#24314) Move drone cron pipelines to (GitHub) Actions. As these are mostly compatible with Gitea Actions, when we start to dogfood, these will already be migrated.
2023-04-26 03:32:49 +02:00
on:
on schedule
2023-04-26 03:38:33 +02:00
schedule:
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 03:21:28 +02:00
- cron: "7 0 * * 1" # every Monday at 00:07 UTC
Build nightly binaries with Actions (#25308) Co-authored-by: silverwind <me@silverwind.io>
2023-06-16 19:00:39 +02:00
workflow_dispatch:
switch to use Actions from drone for cron (#24314) Move drone cron pipelines to (GitHub) Actions. As these are mostly compatible with Gitea Actions, when we start to dogfood, these will already be migrated.
2023-04-26 03:32:49 +02:00
jobs:
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 03:21:28 +02:00
cron-licenses:
switch to use Actions from drone for cron (#24314) Move drone cron pipelines to (GitHub) Actions. As these are mostly compatible with Gitea Actions, when we start to dogfood, these will already be migrated.
2023-04-26 03:32:49 +02:00
runs-on: ubuntu-latest
Don't run build and test if only docs changed (#24530) Co-authored-by: techknowlogick <techknowlogick@gitea.io>
2023-05-16 04:53:18 +02:00
if: github.repository == 'go-gitea/gitea'
switch to use Actions from drone for cron (#24314) Move drone cron pipelines to (GitHub) Actions. As these are mostly compatible with Gitea Actions, when we start to dogfood, these will already be migrated.
2023-04-26 03:32:49 +02:00
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 17:06:27 +02: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 06:31:04 +01:00
- uses: actions/setup-go@v5
switch to use Actions from drone for cron (#24314) Move drone cron pipelines to (GitHub) Actions. As these are mostly compatible with Gitea Actions, when we start to dogfood, these will already be migrated.
2023-04-26 03:32:49 +02: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 12:24:54 +02:00
go-version-file: go.mod
Fix setup-go actions (#25167) 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.
2023-06-09 09:33:48 +02: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 03:21:28 +02:00
- run: make generate-license generate-gitignore
timeout-minutes: 40
switch to use Actions from drone for cron (#24314) Move drone cron pipelines to (GitHub) Actions. As these are mostly compatible with Gitea Actions, when we start to dogfood, these will already be migrated.
2023-04-26 03:32:49 +02:00
- name: push translations to repo
Bump workflows in github actions (#27836) All major version upgrades are related to using Node v20 as default runtime
2023-10-30 08:56:43 +01:00
uses: appleboy/git-push-action@v0.0.3
switch to use Actions from drone for cron (#24314) Move drone cron pipelines to (GitHub) Actions. As these are mostly compatible with Gitea Actions, when we start to dogfood, these will already be migrated.
2023-04-26 03:32:49 +02:00
with:
author_email: "teabot@gitea.io"
author_name: GiteaBot
branch: main
commit: true
commit_message: "[skip ci] Updated licenses and gitignores"
remote: "git@github.com:go-gitea/gitea.git"
ssh_key: ${{ secrets.DEPLOY_KEY }}
Reference in New Issue Copy Permalink