forgejo/docs
31
58
Fork
You've already forked docs
249

doc: document run-name in Forgejo Actions reference #2020

Merged
mahlzahn merged 3 commits from OFHansen/docs:document-run-name into next 2026年07月07日 10:11:00 +02:00
Contributor
Copy link

This PR adds documentation for how to use run-name for workflow titles, to be introduced with Forgejo PR 13114.

This PR adds documentation for how to use `run-name` for workflow titles, to be introduced with Forgejo PR [13114](https://codeberg.org/forgejo/forgejo/pulls/13114).
doc: document run-name in Forgejo Actions reference
Some checks failed
pr / preview (pull_request) Has been cancelled
337fd23aa3
aahlenst left a comment
Copy link

Thanks!

Thanks!
@ -21,1 +21,4 @@
### `run-name`
An optional name for the individual workflow runs generated from the workflow. This name is displayed in the list of workflow runs in a project's Actions tab. If omitted, or if it evaluates to an empty string, the default title is used instead (e.g. the commit message for `push` events, or the workflow `name` for manually dispatched runs).
Member
Copy link

name for individual workflow runs (without "the" before individual). I'm not a fan of e.g. because that's not universally understood.

name for individual workflow runs (without "the" before individual). I'm not a fan of `e.g.` because that's not universally understood.
klausfyhn marked this conversation as resolved
@ -22,0 +23,4 @@
An optional name for the individual workflow runs generated from the workflow. This name is displayed in the list of workflow runs in a project's Actions tab. If omitted, or if it evaluates to an empty string, the default title is used instead (e.g. the commit message for `push` events, or the workflow `name` for manually dispatched runs).
`run-name` is evaluated once, server-side, when the run is created. It can use expressions, and can reference the [contexts](#contexts) `forgejo`/`github`, `inputs`, and `vars`:
Member
Copy link

forgejo, github instead of forgejo/github because one day they won't be identical 🤞

`forgejo, github` instead of `forgejo/github` because one day they won't be identical 🤞
klausfyhn marked this conversation as resolved
fix comments from aahlenst
Some checks failed
pr / preview (pull_request) Failing after 35s
f1f26b5f21
Merge branch 'next' into document-run-name
All checks were successful
pr / preview (pull_request) Successful in 1m31s
backport / backporting (pull_request_target) Has been skipped
2d17da4084
Preview ready: https://forgejo.preview.codeberg.page/docs@2020/docs/next
<!--PR-PREVIEW-MARKER-->Preview ready: https://forgejo.preview.codeberg.page/docs@2020/docs/next
klausfyhn changed title from (削除) WIP: doc: document run-name in Forgejo Actions reference (削除ここまで) to doc: document run-name in Forgejo Actions reference 2026年06月22日 14:26:11 +02:00
mahlzahn changed title from (削除) doc: document run-name in Forgejo Actions reference (削除ここまで) to WIP: doc: document run-name in Forgejo Actions reference 2026年06月22日 14:42:56 +02:00

Thanks for your contribution. Marking as WIP as long as Forgejo isn't merged, yet. When it is merged, feel free to remove the WIP prefix again, please!

Thanks for your contribution. Marking as WIP as long as Forgejo isn't merged, yet. When it is merged, feel free to remove the WIP prefix again, please!
OFHansen changed title from (削除) WIP: doc: document run-name in Forgejo Actions reference (削除ここまで) to doc: document run-name in Forgejo Actions reference 2026年07月07日 09:58:59 +02:00
Sign in to join this conversation.
No reviewers
Labels
Clear labels
404
Broken links or missing content
backport/v1.19
Changes which should be backported to the v1.19 docs

Archived

backport/v1.20
Changes which should be backported to the v1.20 docs

Archived

backport/v1.21
Changes which should be backported to the v1.21 docs

Archived

backport/v10.0
Automated backport to v10.0

Archived

backport/v11.0
Automated backport to v11.0
backport/v12.0
Automated backport to v12.0

Archived

backport/v13.0
Automated backport to v13.0

Archived

backport/v14.0
Automated backport to v14.0

Archived

backport/v15.0
Automated backport to v15.0
backport/v16.0
Automated backport to v16.0
backport/v7.0
Automated backport to the v7.0 docs

Archived

backport/v8.0
Automated backport to the v8.0 docs

Archived

backport/v9.0
Automated backport to the v9.0 docs

Archived

good first issue
This issue is suitable for "drive-by contributors" wanting to contribute for the first time, and fixing it should be straightforward.
meta
Tooling and processes for maintaining the docs
new docs
Content to be added to the documentation

Archived

User research - Accessibility
Requires input about accessibility features, likely involves user testing.
User research - Blocked
Do not pick as-is! We are happy if you can help, but please coordinate with ongoing redesign in this area.
User research - Community
Community features, such as discovering other people's work or otherwise feeling welcome on a Forgejo instance.
User research - Config (instance)
Instance-wide configuration, authentication and other admin-only needs.
User research - Errors
How to deal with errors in the application and write helpful error messages.
User research - Filters
How filter and search is being worked with.
User research - Future backlog
The issue might be inspiring for future design work.
User research - Git workflow
AGit, fork-based and new Git workflow, PR creation etc
User research - Labels
Active research about Labels
User research - Moderation
Moderation Featuers for Admins are undergoing active User Research
User research - Needs input
Use this label to let the User Research team know their input is requested.
User research - Notifications/Dashboard
Research on how users should know what to do next.
User research - Rendering
Text rendering, markup languages etc
User research - Repo creation
Active research about the New Repo dialog.
User research - Repo units
The repo sections, disabling them and the "Add more" button.
User research - Security
User research - Settings (in-app)
How to structure in-app settings in the future?
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
5 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
forgejo/docs!2020
Reference in a new issue
forgejo/docs
No description provided.
Delete branch "OFHansen/docs:document-run-name"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?