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
{{ message }}
This repository was archived by the owner on Dec 2, 2020. It is now read-only.
Repository navigation
This repository was archived by the owner on Dec 2, 2020. It is now read-only.
Hi, @dpb587.
Thank you for the answer. I'm trying to put status to my repo. API token is 100% right cause previously I was able to push status to that repo with a simple Go program. Basically I'm trying to do this:
I don't think I have seen this error before and, unfortunately, it's not easy to debug right now. Quickly reviewing some of the code, I think this could, theoretically, occur if builder is working off a different branch than repo-status was. You might want to make sure repo-status is configured with the branch option if you're using something other than master for builder.
I was also getting this error upon moving a git repo from organisation to organisation and I had forgotten to apply the changes on the resource's config.
Activity
dpb587 commentedon Nov 7, 2018
What operation is this occurring during: check, get, put? Are you sure your API token user has permissions for the repository you’re trying to edit?
kobylyanskiy commentedon Nov 7, 2018
Hi, @dpb587.
Thank you for the answer. I'm trying to put status to my repo. API token is 100% right cause previously I was able to push status to that repo with a simple Go program. Basically I'm trying to do this:
dpb587 commentedon Dec 2, 2018
I don't think I have seen this error before and, unfortunately, it's not easy to debug right now. Quickly reviewing some of the code, I think this could, theoretically, occur if
builderis working off a different branch thanrepo-statuswas. You might want to make surerepo-statusis configured with thebranchoption if you're using something other thanmasterforbuilder.aleveille commentedon Jun 13, 2019
For what it's worth, the original issue might be fixed by any of:
mohsen0 commentedon Aug 15, 2019
I am getting this in check
luispabon commentedon Sep 27, 2019
I was also getting this error upon moving a git repo from organisation to organisation and I had forgotten to apply the changes on the resource's config.
f0o commentedon Nov 17, 2020
Having the same issue. The status gets set correctly but it still throws that error.
out of curiosity, is this repo even maintained?