fix(review): neutralise log markers, flag command substitution #56
zfarrellAnnotations
10 errors
|
review
` in the real log. If you need the exact line, `Read` the file.
|
|
review
` from an already-timestamped log.
|
|
review
` and survived on `::error::`, and all
|
|
review
`.
|
|
review
` from a log whose every line the API has already timestamped.
|
|
review
` and none was a `::`. A leading `+`, a timestamp, or a markdown backtick
|
|
review
this is not really an error` -> the `+` was consumed, annotation fired
|
|
review
`; the run still concluded success, so what this costs is a red mark on
|
|
review
` line — rather than to the frontloaded context, and that next paragraph is the one that stops a reviewer reading an empty CI block as a green one. Moving the sanitiser paragraph below line 18 keeps the pair adjacent and costs nothing, since nothing in it depends on being read first. (Same nit applies to the identical insertion in README, which is prose and not prompt.)
|
|
review
this is not really an error` at column 1 — it is the case the old rule would have prefixed and the new rule respaces instead. The genuinely mid-line assertions are the backtick one two lines below and the timestamped job-log one at 427. As written the description makes the suite read as if line-leading `##[` were untested.
|
Artifacts
Produced during runtime
| Name | Size | Digest | |
|---|---|---|---|
|
claude-tool-usage-pr-26
Expired
|
461 Bytes |
sha256:9567d66e5574cba503c8f3b437731fc11e2ec1e8c94f6ec99b30f92a04261c08
|
|