You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hey and thanks for the issue! The exit status 128 suggests to me that it is an exit code from running git commands, but anything that can return an error usually adds some context via fmt.Errorf("something: %s", err). I.e., your error message should read something like get failed: <reason>: exit status 128 if you are running on the latest dev tag?
So I'm wondering, do you still have this issue or did Concourse suddenly discover a newer SHA for the resource? If so, are you hitting some kind of Docker hub cache? 😂
I think it was a problem with git configuration, as I can run it locally when not run though concourse. I'll close this, as it won't be a problem with github-pr-resource
I am getting
get failed: exit status 128
when trying to run a pipeline, the relevant parts of which are here:But the only output I'm getting is:
I have made sure that the user associated with the access token has write permissions on the repo (not sure if this is actually needed)
I have looked through #35, which resulted in me attempting this with tags of:
v0.6.0
,v11.0.0
anddev
The text was updated successfully, but these errors were encountered: