Please don't spam @ Gedan. Also, she has other priorities that come before the public github she will do it if she finds time to do it
Not sure if two people doing it really counts as spamming yet.Please don't spam @ Gedan. Also, she has other priorities that come before the public github she will do it if she finds time to do it
git push <remote> <commit hash>:master
git remote add public_github https://github.com/OXOIndustries/TiTS-Public.git
git push public_github <revision hash>:master
Nip the problem in the bud before it becomes oneNot sure if two people doing it really counts as spamming yet.
OK.Nip the problem in the bud before it becomes one
It's been like three days please give us the source code. How do you expect me to keep the wiki up to date without it?
Increase the salt to force them to release the code (or at least give a reason for not releasing with an ETA)
OK.
It just seems a little strange to me that you, original author of this salt thread, apparently aren't at all salty that we haven't gotten a git push in two months now (although it's only one month since we were supposed to get one last.)
At this point I am still salty but kind of resigned to it and only checking in every week or so.
Your original requests still don't feel unreasonable to me, especially after a month rather than a simple three days:
Rooting for you. Public build is live.The ship update that was released at that time was a rather major update that I wanted to work on, so i got rather impatient. Although I will bug them extremely hard a soon as the next public goes online though.
I'm pretty sure Fen, Savin, and Gedan don't get notifications from being tagged in posts so people don't waste their time. Just pm her if you actually want it to get done.Also @Gedan please update the source code
Ah, that was CoC2. I'm dumb. My bad.I don't see it
To be precise: fen committed the changes to the branch in his local repo on 10 dec, but only pushed the changes in the past twelve hours or so. (And no, there's no way to show within git when a change was actually pushed, because git is terrible.)Switch the branch from "master" to "public", the latter was updated with 0.8.040 code, apparently on 10th december. That's recent enough, but I only just now found out it was updated at all. I wish the public github was less of a mess, huge delays and sometimes updates go on the default branch, other times onto the second one.
Ah, that explains a lot, thanks!To be precise: fen committed the changes to the branch in his local repo on 10 dec, but only pushed the changes in the past twelve hours or so. (And no, there's no way to show within git when a change was actually pushed, because git is terrible.)