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

Document the runner context and merge with the environment variables section #1777

Merged
mfenniak merged 2 commits from msrd0/forgejo-docs:runner-context into next 2026年02月15日 23:54:18 +01:00
Member
Copy link

Fixes #1776

Fixes #1776
aahlenst left a comment
Copy link

Thanks a lot for your PR! I've added some comments for your consideration.

Thanks a lot for your PR! I've added some comments for your consideration.
@ -1384,0 +1393,4 @@
| Name | Environment Variable | Description |
| ------------------- | -------------------- | ----------- |
| `runner.os` | `RUNNER_OS` | The operating system of the runner, e.g. `Linux` |
| `runner.arch` | `RUNNER_ARCH` | The cpu architecture of the runner |
Member
Copy link

"CPU" instead of "cpu".

It might make sense to include the possible values or at least the naming scheme that is being used. Unfortunately, it's not defined for any other platforms and Forgejo Runner returns whatever docker info spits out which isn't good. 🤔

"CPU" instead of "cpu". It might make sense to include the [possible values](https://github.com/github/docs/blob/main/data/reusables/actions/runner-arch-description.md) or at least the naming scheme that is being used. Unfortunately, it's not defined for any other platforms and Forgejo Runner returns whatever `docker info` spits out which isn't good. 🤔
msrd0 marked this conversation as resolved
@ -1384,0 +1394,4 @@
| ------------------- | -------------------- | ----------- |
| `runner.os` | `RUNNER_OS` | The operating system of the runner, e.g. `Linux` |
| `runner.arch` | `RUNNER_ARCH` | The cpu architecture of the runner |
| `runner.temp` | `RUNNER_TMP` | This is a temporary directory provided by the runner. It's hardcoded to `/tmp`. |
Member
Copy link

Please drop "It's hardcoded to /tmp." That's an implementation detail and can change.

Please drop "It's hardcoded to `/tmp.`" That's an implementation detail and can change.
msrd0 marked this conversation as resolved

Thanks for taking this on. Please check the Actions results on the PR in addition to the review comments, as the docs linter has a couple small complaints that need to be resolved. 🙂

Thanks for taking this on. Please check the Actions results on the PR in addition to the review comments, as the docs linter has a couple small complaints that need to be resolved. 🙂
msrd0 force-pushed runner-context from 2550cf3c02
Some checks failed
pr / preview (pull_request_target) Failing after 21s
to 0ddde7593f
Some checks failed
pr / preview (pull_request_target) Failing after 19s
2026年02月10日 17:30:35 +01:00 Compare
Author
Member
Copy link

@mfenniak Feel free to run whatever javascript based pretty-printer the actions complain about on this PR. I am not going to bother with anything javascript, and I am not manually going to add that many spaces for a pointless alignment of the last | of the table.

@mfenniak Feel free to run whatever javascript based pretty-printer the actions complain about on this PR. I am not going to bother with anything javascript, and I am not manually going to add that many spaces for a pointless alignment of the last `|` of the table.

You can just copy and paste the output from the linter failure and remove the leading diff marks +.

You can just copy and paste the output from the linter failure and remove the leading diff marks `+`.
Make linter happy
All checks were successful
pr / preview (pull_request_target) Successful in 2m20s
backport / backporting (pull_request_target) Has been skipped
1864f7f8ec

Linter should now be okay, @aahlenst @mfenniak good to be merged?

Linter should now be okay, @aahlenst @mfenniak good to be merged?
Collaborator
Copy link

Preview ready: https://forgejo.codeberg.page/@docs_pull_1777/

Preview ready: https://forgejo.codeberg.page/@docs_pull_1777/
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!1777
Reference in a new issue
forgejo/docs
No description provided.
Delete branch "msrd0/forgejo-docs:runner-context"

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?