game-ci / game-ci/documentation
Logging documentation page describes options that do not exist
- Dominant language
- MDX
- Stars
- 243
- Forks
- 130
- Avg merge
- 15d 42m
- Merged PRs (30d)
- 1
Description
On https://github.com/game-ci/documentation/blob/main/docs/03-github-orchestrator/07-advanced-topics/22-unity-log-collection.mdx it describes logging options available to `unity-builder`. However, there is no logging options in that workflow.
> Add `collectUnityLogs: true` to your existing `unity-builder` (or `unity-orchestrator`) step. Everything else is automatic:
See https://github.com/game-ci/unity-builder/blob/main/action.yml
Contributor guide
Research direction
Open docs/03-github-orchestrator/07-advanced-topics/22-unity-log-collection.mdx and compare its logging guidance with unity-builder/action.yml. Confirm which documented options are absent, then update the page so it describes the available workflow accurately and no longer recommends nonexistent options.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- unity
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 75/100