The best time to leave github has past, but the second best time is Monday morning.
Dump microsoft. They are part of the problem.
#BDSUSA #BDS_usa #DumpGithub #BoycottMicrosoft #BoycottAmerica
Sweet, I got it working! Now, I can use my codeberg repo "junkdrawer" as a semi-replacement for github gists.
It's not super clear from the API documentation, but for a file that does not exist yet, you have to POST it; for a file that exists, you have to PUT it and include the sha1sum of the file to be replaced.
I've used junk.py to post itself to my junkdrawer: https://codeberg.org/jepler/junkdrawer/src/branch/main/aygdu2e9/junk.py
This script conforms to PEP723 so you can run it with uv run.
no non-archived source repositories left! (though I do have one organization with a repository I care about...) https://github.com/jepler?tab=repositories&type=source
I moved textual-totp to codeberg today. I'm down to just 4 "source" repositories on github, 1 to transfer to an organization staying on github, 1 needing migration to codeberg, and 2 to just allow to become defunct...
Another github project archived, not yet moved to codeberg: https://github.com/jepler/leapseconddata
leapseconddata is a relatively straightforward library to access information about past and announced leap seconds from Python code (as well as a small command line program to access the same data)
It's a pure Python program compatible with Python 3.9 and up (last release tested 3.13).
It's somewhat likely that there'll never be another leap second, as various international bodies are working on proposals to end the practice by 2030. (there might be something else in the future, like a leap hour, but only after everyone working on the new definition of UTC is dead so they for sure won't have to deal with it)
(and anyway the program doesn't rely on a bundled version of the data, so even a new leap second doesn't create a need for a new release)
I do use it in another project (wwvbpy) so if there's a need in the future I'll revive it on codeberg to make some future release.
Another #gitHub repo marked "archived". No, I'm not moving this one to #codeberg
Back in 2023 I wanted to learn textual, and I decided writing an LLM interface was a good choice (not what I'd do in 2025, but well, the world and I were both different 2 1/2 years ago).
These days, I'm cough not so excited about the prospect of LLMs, so as I work to curtail my active repos on github it was an easy decision to just not move this one over but simply to archive it.
I'm glad I learned textual, though, and up soon is migrating my actually useful textual project, a desktop TOTP app.
Current status: 6 non-archived, non-fork repos associated with my github user.
I've moved another project of mine to codeberg, and also I'm hosting its pages using grebedoc.
It's an anagram helper that can run in your web browser. Live version: https://jepler.grebedoc.dev/anagram/ Source: https://codeberg.org/jepler/anagram
OK, all aspects of the "wwvbpy" project that formerly used github actions are moved off of github to codeberg:
.. all implemented in a language very reminiscent of github actions yml, but with tweaks to trim the fat and run with forgejo actions on the codeberg-tiny runner.
The next stable release of wwvbpy will be made from codeberg, and will also drop support for Python 3.9.
I offiically moved my first project to codeberg this weekend: https://codeberg.org/jepler/wwvbpy/
todo: get CI working, including releasing from codeberg to pypi.
(previously: I soft-moved m68k-micropython but didn't follow through with archiving it on github)
Stylus
Charles ☭ 
is a Green
