@amkuchta would it be possible to get a new SHA for this? Thank you so much for your patience.
@packenbush, if you could also provide a SHA that is failing for you? That could help us narrow down the issue.
@tom apologies, things have been hectic the past few days. I am generating a new SHA now and will submit it over in a few moments!
@amkuchta apologies I was dealing with COVID the past few weeks. I hate to do this again, but can we get a new SHA?
@tom I hope this doesnāt violate a community standard, but holy hell I am sorry to hear that, and I hope that you are doing well now!
I am currently at my day job, but will create a new SHA for you this evening once I am off!
+1 here. Iām also facing this problem. It used to work with my GitLab project (which is NOT public, but it did work), and now it stopped. Let me know if I can also help in providing some log by my side.
Hi @amkuchta, thanks for the SHA here. I checked on GitLab, but Iāll be honest Iām not super familiar with it, so correct me if Iām wrong. I donāt think that commit is part of a merge request. If thatās the case, thatās probably why we are not sending a comment for that particular commit.
Would you be able to confirm that it is a part of a merge request (and just shoot the link over) or that it isnāt and could you update with a commit that is part of one?
@tom it is definitely a part of a merge request; the link for it can be found here:
It should be the latest commit in that MR. Hope this helps!
@amkuchta thatās so strange, I canāt see that link (I get a 404)
My GitLab knowledge is pretty limited, do you know if thereās a setting that prevents users from seeing merge requests? I know the repo is public, so thatās a bit strange to me.
@tom I made a quick update - see if you can get to it now.
I had it set so that only Project Members could see Merge Requests.
@amkuchta that works! Would you be able to push a commit to it now, Iād like to see if there was a permissions issue there.
That did it! Thatās weird to me, considering itās supposed to be posting under my accountā¦ and I am a memberā¦
@tom Iād like to make the repo private - if I were to do that and generate another commit, could you try to track it? That would also help to address @isorensenās issues.
1 Like
@amkuchta, huhā¦ Iām surprised that was what was needed. Thanks for your patience.
Feel free to make the repo private, I should be able to track it now.