latest 18 messages by terabyte

+ [2019-10-10T12:06:07Z] terabyte depends if you're generating it or using it...
+ [2019-06-21T11:27:41Z] terabyte fix for my issue was to not mention the commitish when creating a release where a tag already exists. the API docs say it ignores this field in the case where the tag exists, but it doesn't ignore it, it throws a vague exception.
+ [2019-06-21T10:36:45Z] terabyte looks like the github api doesn't understand that a tag is a commitish....
+ [2019-06-21T09:44:50Z] terabyte the exact error: {"message":"Validation Failed","errors":[{"resource":"Release","code":"invalid","field":"target_commitish"}]
+ [2019-06-21T09:43:54Z] terabyte hey, on the github release api, i have a tag for a project called wallow which is 'wallow-1.1', is a git tag also a commitish? because when i tried to create a release, it complained that it wasn't a valid commitish...
+ [2019-06-16T19:08:39Z] terabyte ok great! thanks
+ [2019-06-16T19:05:00Z] terabyte asking because i'd rather use a library to deal with the substitution correctly, but i've no idea what this is called...
+ [2019-06-16T19:03:49Z] terabyte Hi, from the API docs, an upload URL sent in response to creating a release can contain this: {?name,label} format substitution. I guess that's ?name=file.zip but what is this '{?name,label}' style of substitution called?
+ [2015-10-06T22:32:29Z] terabyte I need to fill out the state field in the oauth query, question is, if i generate a random number, and redirect to some other website, how do i remember the random number so that when i'm redirected back to the site I can verify the original against the given.
+ [2015-10-06T22:06:49Z] terabyte I need to fill out the state field in the oauth query, question is, if i generate a random number, and redirect to some other website, how do i remember the random number so that when i'm redirected back to the site I can verify the original against the given.
+ [2015-10-06T04:54:33Z] terabyte is it safe for the bearer token to appear in the urlbar? I set the callback to /login, so now in my history I can see /login?code=secretBearerToken.
+ [2015-10-06T01:55:55Z] terabyte wolfman2000 are you able to call any part of the api that requires an key successfully?
+ [2015-10-06T01:16:23Z] terabyte if clientside angularjs generates the nonse, how does remember the state such that it can compare it later?
+ [2015-10-06T01:15:44Z] terabyte in a server signed cookie?
+ [2015-10-06T01:15:44Z] terabyte in the github oauth flow, I've blindly accepted the need for the "state" variable to prevent certain attacks, but I'm not clear, who generates that variable and where should it be stored? So for example in an angularjs app where the app only wishes to authenticate the user, is it the clientside angularjs that should generate the nonce word, or should a call to a backend api be made, and stored