gitforge/modules/structs
Andreas Ahlenstorf 5e1c13f50e feat: allow runners to request a particular job (#11676)
Forgejo Runner can optionally ask for a particular job. Example: `forgejo-runner one-job --handle 9d52c7d8-aebe-426b-b015-dd453aacaada`. This change adds the necessary job filtering to Forgejo.

See https://code.forgejo.org/forgejo/forgejo-actions-feature-requests/issues/76 for the motivation and design considerations.

PR for the extension of the runner protocol: https://code.forgejo.org/forgejo/actions-proto/pulls/18

Related change in Forgejo Runner with usage example: https://code.forgejo.org/forgejo/runner/pulls/1443

## Checklist

The [contributor guide](https://forgejo.org/docs/next/contributor/) contains information that will be helpful to first time contributors. 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...
  - [x] 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.
- [x] 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.

<!--start release-notes-assistant-->

## Release notes
<!--URL:https://codeberg.org/forgejo/forgejo-->
- Features
  - [PR](https://codeberg.org/forgejo/forgejo/pulls/11676): <!--number 11676 --><!--line 0 --><!--description YWxsb3cgcnVubmVycyB0byByZXF1ZXN0IGEgcGFydGljdWxhciBqb2I=-->allow runners to request a particular job<!--description-->
<!--end release-notes-assistant-->

Reviewed-on: https://codeberg.org/forgejo/forgejo/pulls/11676
Reviewed-by: Mathieu Fenniak <mfenniak@noreply.codeberg.org>
Co-authored-by: Andreas Ahlenstorf <andreas@ahlenstorf.ch>
Co-committed-by: Andreas Ahlenstorf <andreas@ahlenstorf.ch>
2026-03-25 17:27:05 +01:00
..
action.go feat: allow runners to request a particular job (#11676) 2026-03-25 17:27:05 +01:00
activity.go
activitypub.go
admin_user.go feat: Add support for administrators to set email visibility on user accounts (#9668) 2025-10-15 03:21:15 +02:00
attachment.go
commit_status.go
commit_status_test.go
cron.go
doc.go
fork.go
git_blob.go
git_hook.go
hook.go
issue.go chore: fix typos throughout the codebase (#10753) 2026-01-26 22:57:33 +01:00
issue_comment.go feat(api): more verbose error messages and swagger comments for posting issue comments (#11368) 2026-03-07 23:16:20 +01:00
issue_label.go
issue_milestone.go
issue_reaction.go
issue_stopwatch.go
issue_test.go
issue_tracked_time.go
lfs_lock.go
mirror.go
miscellaneous.go
moderation.go
nodeinfo.go
notifications.go
org.go
org_member.go
org_team.go fix: correct malformed CreateTeamOption example (#11093) 2026-02-16 05:55:20 +01:00
package.go
pull.go
pull_review.go
quota.go
release.go
repo.go feat: add wiki git info to API (#11589) 2026-03-19 01:21:50 +01:00
repo_actions.go feat: implement ephemeral runners (#9962) 2026-02-16 18:56:56 +01:00
repo_branch.go
repo_collaborator.go
repo_commit.go
repo_compare.go
repo_file.go
repo_flags.go
repo_key.go
repo_note.go
repo_refs.go
repo_tag.go
repo_topic.go
repo_tree.go
repo_watch.go
repo_wiki.go
runner.go chore: remove field ephemeral from runner registration response (#11350) 2026-02-18 16:49:44 +01:00
secret.go fix: normalize secrets consistently, display accurate help (#11052) 2026-02-09 17:02:18 +01:00
settings.go
status.go
task.go
user.go
user_app.go feat: read, create, & delete repo-specific access tokens via API (#11504) 2026-03-07 21:55:08 +01:00
user_email.go fix: use ValidateEmail as binding across web forms 2024-08-28 22:25:17 -06:00
user_gpgkey.go
user_key.go
variable.go fix: normalize secrets consistently, display accurate help (#11052) 2026-02-09 17:02:18 +01:00
visible_type.go
workflow.go