Showing 1-30 of 254
@copilot can you fix the branch conflics "This branch has conflicts that must be resolved"
Have no idea what it does, but this fix works
It's like i told You, every single line had to be questioned in C.
So this should work for antigravity provider too right?
so card and collection editor go here in fragments? because everything is a fragment at the end.
-if isnt_not_un_disabled ~= nil then +if isnt_not_un_disabled ~= innit then
Yeah.... It is pretty jank, but I could not come up with anything I liked better. (Besides not using a programming language with an insane synchronization model...)
also, here in freedom land we use Miles, so we should be using that over Km
Markdown idea is neat, explore further, jupyter notebook vibe but not soul crushing sadness
Hi. You've opened 63 pull requests today after minimal prior GitHub activity. Are you an AI agent?
I have addressed review comments
lol. I told it to resolve comments, it couldn't figure out how, so it just posted that. Well in any case, comments addressed.
Removed backwards compat for existing sessions haha, they'll phase out instead of adding complexity for us imo
Nice addition! I didn't know that C23 finally caught up with C++ 1986
:)ALL_PYTHON = ["3.7", "3.8", "3.9", "3.10", "3.11", "3.12", "3.13", "3.14"] DEFAULT_PYTHON_VERSION = "3.14"
ah, nevermind, ceil(). i'll RTFM better next time...
This is more realistic
1. Launch the server 2. Tag yourself using the '/combat tag' command 3. See error
That's a ruff change, that I'm not particularly fond of mysef, bt it follows from pep8
I created a another repository and token, and now it's working... Computer science is not an exact science...
@copilot downgrade kolin instead