Let me try that.  I did originally have develop instead of development 
because another repo used that convention and I got a 404.

Thanks,

Cade

On Monday, August 26, 2019 at 1:50:10 PM UTC-5, Mark S. wrote:
>
> Does it save if you switch to master?
>
> On mine, I got everything to work, including working on development 
> branch. Then I downloaded and reloaded the file, and after that
> I couldn't get it work on "development". I had the same 409 message. Then 
> I switched back to "master" and it worked OK again.
>
> Suggests there's a bug somewhere, that retains "master" as a default.
>
> Good luck!
>
> On Monday, August 26, 2019 at 10:59:01 AM UTC-7, Cade Roux wrote:
>>
>> Sure.
>>
>> I have a token in the password
>>
>>
>> This is what GitHub looks like in the Web interface:
>>
>> [image: Capture.PNG]
>>
>>
>> On Monday, August 26, 2019 at 12:52:14 PM UTC-5, Mark S. wrote:
>>>
>>> It might help if you could show a screen shot of your set up.
>>>
>>> I found that you MUST specify
>>>
>>> Path to target file (e.g. /wiki/)
>>>>
>>>
>>> That is, that field can not be blank. I was using the top level, so put 
>>> in /
>>>
>>> Good luck!
>>>
>>> On Monday, August 26, 2019 at 10:40:19 AM UTC-7, Cade Roux wrote:
>>>>
>>>> I have a TW file in GitHub.  I set up all the parameters for GitHub 
>>>> saving, they seem to be correct.  I got some errors in XMLHttpRequest 409, 
>>>> which perhaps indicates that a commit was not allowed due to a conflict?  
>>>> Sometimes it gives that error or sometimes it just sits there with the red 
>>>> check in a circle.  Either way, nothing is committing to GitHub.
>>>>
>>>> Any tips on what to look at?
>>>>
>>>> Thanks,
>>>>
>>>> Cade
>>>>
>>>

-- 
You received this message because you are subscribed to the Google Groups 
"TiddlyWiki" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/tiddlywiki/c96ce77b-f68e-407e-8d06-fbb448e7a944%40googlegroups.com.

Reply via email to