Tootfinder

It’s Wednesday, and we’ve got a new demo.
https://retrofit.sh/demos/pull-and-sync/
In the demo we simulate a standard developer flow.

Rolling out some documentation QA checks for my repositories. So now I have a ton of open PR's with failing CI pipelines over small documentation issues. While I still have my doubts about AI in general for a bag of reasons. Being able to press a button to get it fixed vs opening each repo locally, fetch & pull, fix the issue, git push --force-with-lease and wait for the CI to go green.

A pipeline failed because a directory "already existed" — except it didn't, not when I looked. Turns out screen had quietly let two copies of the same self-hosted Bitbucket runner run side by side for who knows how long, and Bitbucket never once complained about it.

Two Bitbucket Pipelines runners, one ID, and a git clone error for a directory that wasn't there - Winkelwagen GmbH - an ecommerce agency
A pipeline run failed with this:

I wrote a proposal in the #CoSocialCa members forum about making services we already run on @… for general co-op operations.
Git hosting (we run @…

With apologies to those with red/blue colour blindness here is a scatter #plot showing the age of commits mentioned by the Fixes: tag in #qemu's #git My initial takeaways are we've been getting better at…

OH on slack:
> PSA this just bit me and ate a lot of time:
>
> git 2.55.0 changes some credential behaviors and breaks logins like pip install git https://${GITHUB_TOKEN}@github.com/... they must be replaced with pip install git https://x-access-token:${GITHUB_TOKEN}@github.com/...
#git #pip #github