Add examples of CI environment variable values

[hg]

Not sure if you're interested in this; if not, I'll just keep it for my own reference.

I find it useful when writing build scripts because sometimes the exact way a value is formatted is not obvious, and you have to run a test job to find out.

Drone has something similar, but in a much less convenient form, spread over dozens of pages:

• https://docs.drone.io/pipeline/environment/reference/drone-commit/
• https://docs.drone.io/pipeline/environment/reference/

etc.

[woodpecker-bot]

Deployment of preview was torn down

[pat-s]

I like the idea in general.
I don't think we should format all values as code, I'd prefer to have them as plain text instead.

[qwerty287]

I wouldn't say so... I prefer code

[pat-s]

Then let's hear more opinions - @woodpecker-ci/maintainers

[hg]

Here's how they get rendered (at least by GitHub): code, plain text, the middle ground (wrap list items and URLs that were not parsed correctly).

[qwerty287]

I still prefer code (except lists, the separator shouldn't be part of the code)

[qwerty287]

It looks like @anbraten and @xoxys prefer code so I'd go on with this. You have to run prettier though, this isn't that easy with giyhu suggestions...

[hg]

Thanks, I applied all three and reformatted the file with prettier.