search

crystal-ameba / github-action

A GitHub Action that lints Crystal code with Ameba
MIT License
29 stars 6 forks source link

Create annotations using stdout to avoid GITHUB_TOKEN #19

Open ysbaddaden opened 4 months ago

ysbaddaden commented 4 months ago

Extract from external discussion:

You can create annotations manually by writing some specific markup to stdout

https://github.com/crystal-lang/crystal/issues/14608#issuecomment-2134883762

This mechanism was developed before the capability to create annotations using stdout messages was introduced.

https://github.com/crystal-lang/crystal/issues/14608#issuecomment-2134971680

straight-shoota commented 4 months ago

I believe there must be another way to create annotations attached to code locations in a more structured manner without writing markup to stdout. I don't recall how exactly. It might be related to junit output. We configure that it multiple workflows in https://github.com/crystal-lang/crystal/tree/master/.github/workflows (junit_output=.junit/xxx_spec.xml). So maybe GHA picks up the spec results in the .junit folder? I haven't found anything specific about this in the documentation.