Skip to content

fix: ensure logs use coloured output - #1083

Merged
jamietanna merged 3 commits into
mainfrom
fix/colour
Sep 29, 2026
Merged

jamietanna merged 3 commits into
mainfrom
fix/colour

Conversation

@jamietanna

Copy link
Copy Markdown
Member

In 5be7d62 we removed the TTY
allocation which allowed GitHub Actions to enforce coloured output.

As per suggestion in #970, we can apply a change similar to our GitLab
CI runner0 to set FORCE_COLOR=3, which restores coloured output.

Closes #970

In 5be7d62 we removed the TTY
allocation which allowed GitHub Actions to enforce coloured output.

As per suggestion in #970, we can apply a change similar to our GitLab
CI runner[0] to set `FORCE_COLOR=3`, which restores coloured output.

[0]: https://gitlab.com/renovate-bot/renovate-runner/-/commit/c4bc3c83e13ef47f496e2be8b986b16c1dece0bf
@github-actions
github-actions Bot requested a review from viceice September 29, 2026 13:29
@jamietanna
jamietanna enabled auto-merge (squash) September 29, 2026 13:40
@jamietanna
jamietanna merged commit c368bd1 into main Sep 29, 2026
16 checks passed
@jamietanna
jamietanna deleted the fix/colour branch September 29, 2026 13:47
Mogyuchi added a commit to 4m-mazi/renovate-workflow that referenced this pull request Oct 3, 2026
renovatebot/github-action v46.3.6 now passes FORCE_COLOR=3 to the
container itself (renovatebot/github-action#1083), so the workflow-level
setting is redundant.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Ensure logs use colored output

2 participants