I think the solution here would be to keep error strings themselves of the form

doing a thing

and have whatever writes to the comment itself prepend

Error: <>

Also I have been thinking about this, https://github.com/pkg/errors has been abandoned in favor of improved error wrapping in the stdlib, we should probably transition to that as well 🤔

it is cleaner and consistent with general style guides https://google.github.io/styleguide/go/decisions#error-strings https://go.dev/wiki/CodeReviewComments#error-strings

but the issue is it yields an awkward comment, which is what https://github.com/runatlantis/atlantis/pull/4177 is trying to address

(at least partially)

I think the right solution is for the actual errors to conform to this rule, but then when we write the errors somewhere we say

fmt.Printf("Error: %v", err)

So I think for this PR the options are: 1. Have the user remove

Error:

from the error string and leave the VCS comment as is 2. Leave the

Error:

in the comment and attempt to address the formatting of the comment in a different issue 3. Have the user address the formatting of the comment in this issue