-
Notifications
You must be signed in to change notification settings - Fork 66.7k
Unclear if endColumn is inclusive or exclusive #40038
Copy link
Copy link
Closed as not planned
Labels
Closed as inactiveAutomatically closed by a stale checkAutomatically closed by a stale checkInactiveWill be closed automatically by a stall check if no activity is detected.Will be closed automatically by a stall check if no activity is detected.contentThis issue or pull request belongs to the Docs Content teamThis issue or pull request belongs to the Docs Content teamgithub_actionsPull requests that update GitHub Actions codePull requests that update GitHub Actions code
Metadata
Metadata
Assignees
Labels
Closed as inactiveAutomatically closed by a stale checkAutomatically closed by a stale checkInactiveWill be closed automatically by a stall check if no activity is detected.Will be closed automatically by a stall check if no activity is detected.contentThis issue or pull request belongs to the Docs Content teamThis issue or pull request belongs to the Docs Content teamgithub_actionsPull requests that update GitHub Actions codePull requests that update GitHub Actions code
Type
Fields
Give feedbackNo fields configured for issues without a type.
Code of Conduct
What article on docs.github.com is affected?
https://docs.github.com/en/actions/reference/workflows-and-actions/workflow-commands
What part(s) of the article would you like to see updated?
In the table presented in the Setting a notice message section, the description for
endColumnin theValuecolumn is now:It should also explain whether the 1-based column number is inclusive or exclusive, e.g.
Additional information
Here's one example of evidence where a developer seems to have verified that
endColumnis exclusive:https://github.com/llamastack/llama-stack-k8s-operator/blob/2fa21ea25dc91524d86bfb69c053e16d12d5bd72/hack/check_go_errors.py#L42-L43