[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Error in git-cl creating a new issue
From: |
John Gourlay |
Subject: |
Re: Error in git-cl creating a new issue |
Date: |
Wed, 6 Jan 2016 11:38:46 -0500 |
This was the first time I tried to use git-cl. I made another small
typographical fix to the Contributor’s Guide and submitted the new patch. I got
the same error. I have the Allura server url set correctly, and I have a bearer
token that I obtained following the instructions in the Contributor’s Guide. I
don’t know how to verify that it is actually correct, however.
> On Jan 6, 2016, at 11:24 AM, Trevor Daniels <address@hidden> wrote:
>
>
> Simon, you wrote Wednesday, January 06, 2016 4:05 PM
>
>> The rietveld part is fine. Only the Allura part reliably fails, with the
>> same kind of messages that John reported.
>> I’ve just been creating issues manually.
>
> Well, a 403 HTTP error means the server received and understood
> the request but decided the request was forbidden.
>
> Assuming you have a valid bearer token, see
> https://sourceforge.net/auth/oauth/,
>
> and have set up the full url to the correct page:
> https://sourceforge.net/p/testlilyissues/issues/
>
> I don't know what else might be wrong.
>
> If neither of these are the reason we'll have to wait until
> Phil can take a look.
>
> Trevor
>
>