Andreas Ahlenstorf b29e21a90c fix: use proper ${{ forgejo.ref }} in scheduled workflows (#13081) ... Forgejo uses the plain branch name instead of a so-called fully-formed ref name (`refs/heads/<branch_name>`) when setting the `Ref` property of scheduled workflows, which is wrong. Resolves https://codeberg.org/forgejo/forgejo/issues/13060. ## Checklist The [contributor guide](https://forgejo.org/docs/next/contributor/) contains information that will be helpful to first time contributors. All work and communication must conform to Forgejo's [AI Agreement](https://codeberg.org/forgejo/governance/src/branch/main/AIAgreement.md). There also are a few [conditions for merging Pull Requests in Forgejo repositories](https://codeberg.org/forgejo/governance/src/branch/main/PullRequestsAgreement.md). You are also welcome to join the [Forgejo development chatroom](https://matrix.to/#/#forgejo-development:matrix.org). ### Tests for Go changes (can be removed for JavaScript changes) - I added test coverage for Go changes... - [ ] in their respective `*_test.go` for unit tests. - [x] in the `tests/integration` directory if it involves interactions with a live Forgejo server. - I ran... - [x] `make pr-go` before pushing ### Tests for JavaScript changes (can be removed for Go changes) - I added test coverage for JavaScript changes... - [ ] in `web_src/js/*.test.js` if it can be unit tested. - [ ] in `tests/e2e/*.test.e2e.js` if it requires interactions with a live Forgejo server (see also the [developer guide for JavaScript testing](https://codeberg.org/forgejo/forgejo/src/branch/forgejo/tests/e2e/README.md#end-to-end-tests)). ### Documentation - [ ] I created a pull request [to the documentation](https://codeberg.org/forgejo/docs) to explain to Forgejo users how to use this change. - [ ] I did not document these changes and I do not expect someone else to do it. ### Release notes - [x] This change will be noticed by a Forgejo user or admin (feature, bug fix, performance, etc.). I suggest to include a release note for this change. - [ ] This change is not visible to a Forgejo user or admin (refactor, dependency upgrade, etc.). I think there is no need to add a release note for this change. *The decision if the pull request will be shown in the release notes is up to the mergers / release team.* The content of the `release-notes/<pull request number>.md` file will serve as the basis for the release notes. If the file does not exist, the title of the pull request will be used instead. Reviewed-on: https://codeberg.org/forgejo/forgejo/pulls/13081 Reviewed-by: Mathieu Fenniak <mfenniak@noreply.codeberg.org>		2026-06-15 04:15:07 +02:00
..
TestActionTask_GetTasksByRunnerRequestKey
TestRunner_FindRunnerOptionsToConds
TestRunner_GetVisibleRunnerByID
artifact.go
forgejo.go
forgejo_test.go
main_test.go
pre_execution_errors.go
pre_execution_errors_test.go
run.go
run_job.go
run_job_list.go
run_job_list_test.go
run_job_status_test.go
run_job_test.go
run_list.go
run_list_test.go
run_test.go
runner.go
runner_list.go
runner_test.go
runner_token.go
runner_token_test.go
schedule.go
schedule_spec.go
schedule_spec_list.go
schedule_spec_test.go
schedule_test.go
status.go
task.go
task_list.go
task_output.go
task_step.go
task_test.go
tasks_version.go
user.go
user_test.go
utils.go
utils_test.go
variable.go