#CML in action within #Github Desktop: after pushing changes, the action runs and - once the results are ready - the app gives a notification and displays the generated plots
I've got a main branch and a production branch on #github.
PRs go into main and merge commits are disabled for the repo. When read, main is merged to production where I want a regular merge. This then triggers a jenkins release based on branch name.
This merge works, but maybe there's a better/more visible process.
Dear #github, please don't automatically add new bullshit discussion categories like "polls" without my consent to my project's discussion tracker. We don't do "polls". If SQLAlchemy users want to make "polls" please do it on social media, it is not actionable by maintainers of an OSS project.
In university, one of my favorite modules was operating systems. We handled many different architectures starting from the beginning and working to modern-day systems.
We looked at processing, memory management, interrupts, storage, etc. and often had projects where we had to implement low-level systems.
Even with this knowledge, it always breaks my brain thinking about how bugs like these are found and even more so how we fix them. I am going to go down the #github rabit hole now to see how they did it.
Well done to the #Linux community for their great work.
it'd be really cool, if when i open up my PR on #GitHub if i didn't have to scroll-scroll-scroll-scroll-scroll-scroll-scroll-scroll-scroll-scroll-scroll-scroll-scroll-scroll-scroll-scroll-scroll-scroll-scroll-scroll-scroll-scroll-scroll-scroll-scroll-scroll-scroll-scroll-scroll-scroll
to get to the bottom and find out if it passed CI or not.
Anyone doing #github#actions - does anyone know a way to do dynamic environment variables, at the job level - based on a folder in a #monorepo?
I need to build container images and frontend apps, and pass to them different API paths and keys. At the moment every time an app is added, the secrets and vars need to get added to be passed down into the actions.
#Paramiko's #GitHub repo now has a handful of fancy issue submission templates, courtesy of @btskinn ! 😤🙌🏻✨
Be interesting to see (or…hear about… 🙈😩) if this helps a bit with some of the noisier input.
It must be administrivia day, because I've also spent some time futzing with #ReadTheDocs to see if I can get the "you're not reading the latest version” banners to show up again for my projects. (sadly not yet, even tho I nuked my old tag-versions w/ their API.)
Oh my gosh do I get obsessive, just spent the afternoon tinkering with a #watchy#watchface fork on #github. Added two new watch faces that were stuck behind old broken repo's and fixed a few others. Next I'm going to convert all the US dates into normal person standard and maybe move the project to gitlab.
