+[2019-06-20T11:59:34Z]CraigErI think you've left joanna89, but for anyone else, you're looking for: https://developer.github.com/v3/ +[2019-06-20T12:04:46Z]CraigErSpecifically https://developer.github.com/v3/repos/#create +[2019-06-20T15:29:48Z]dka_hi CraigEr and joanna89 +[2019-06-20T17:43:35Z]maestrojed‘fetch’ lines 13,16, and 19. Also that the master branch uses the remote ‘acct1’, is that proper? acct1 is the most important. https://gist.github.com/maestrojed/dba741d7624bb5a25f3d038fbcce4fe2 +[2019-06-20T17:43:35Z]maestrojedLooking for a little confirmation before I ask my team to make an adjustment. We use a hosting service that manages deployment via a git repo they provide. Additionally I would like to use Github as I like Githubs review and interface tools. I configured my local git with two remotes. For ‘origin’ I added both remote URLs. Seems to work great. Every time I pull or push I do so with both repos. Any reason this is wrong? mostly I am curious about
+[2019-06-21T04:49:27Z]dysfigureddka_: i have a bash script that uses the github api to create repos from the command prompt +[2019-06-21T09:43:54Z]terabytehey, 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-21T09:44:50Z]terabytethe exact error: {"message":"Validation Failed","errors":[{"resource":"Release","code":"invalid","field":"target_commitish"}] +[2019-06-21T10:36:45Z]terabytelooks like the github api doesn't understand that a tag is a commitish.... +[2019-06-21T11:27:41Z]terabytefix 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.