Hey folks, this is an important #security update for #JetBrains users. Please update as soon as possible if you use #GitHub and the integration in the #IDE tools.
You know, that massive hub of public and private software projects that is the de facto home of open source.
The place owned by the same corporation that just tried to sneak a total surveillance system into the most used operating system by end users and business on the planet.
A couple of years ago I showed that we could start replacing this with a truly #decentralised alternative. See: #p2pgit
If you’re working on #oss with #dotnet in #JetBrainsRider, you'll notice that the VCS dropdown shows you if the current branch is tied to a #github PR and allows you to open it in the tool window. Cool!
So #Github just rolled out this fun change to their fancy hover cards (used when referring to people, issues, and comments) which is now killing my productivity:
<a class="d-inline-block" data-hovercard-type="user" href="something" aria-description="Hovercard. Press Alt+Up to activate">...</a>
Hmm, seems[1] people submitting #Linux#kernel pull request in #github for torvalds/linux[2] do not get a helpful "you are wrong here" message[3] from the KernelPRBot any more.
Does anyone know if the service/the bot was abandoned? Or is it just broken?
[Edit] should be working again, see replies! [/Edit]
Sometimes I wonder if the marketing team at #github is mad that #microsoft stole the copilot branding and took it over. Like imagine being the github sales people after Microsoft keeps saying they're bringing copilot to everyone for free. "No you should keep paying us for our copilot, even though we're owned by Microsoft and they are also selling you copilot. They're different copilots."
I am excited to present at the Dev AI conference in Paris on June 19!
I am going to run a workshop about the deployment and monitoring of ML pipelines with free and open-source tools. This includes using tools such as GitHub Actions and Pages, Docker, Python, Quarto, etc.
We've hit 50 stars on GitHub!
A massive thank you for your support and contributions. This milestone is just the beginning, and we can't wait to continue building and growing together!
From #Copilot, to #Azure AI and #Prompty, to their developer first focus, leading #GitHub, #VSCode being the long bet that paid off, to the future of a doctor’s bedside manner assisted with AI.
Microsoft is all-in on AI and Build 2024’s discussions and announcements proves it.
Hi #blind folks, especially software developers! I'm taking part in a #GitHub research meeting and I hope to raise as many #accessibility points as I can. I was told this fact is not at all confidential, so I may gather feedback.
Here's what I remember: multiline comments are inaccessible (eternal story); sometimes menu roles are used where they shouldn't be (watching repos, reactions etc.). Anything else that really bugs you at GitHub? Thanks!
My efforts to put all my #GitHub Action Workflows into a centralized repository and make where to run configurable on the ones for private projects is paying off. Most things can now run on my home cluster, but scaling is still somewhat slow:
Changes:
You can now show a preview of your own profile by tapping on your profile picture
Randomize order of interests, images and prompts
General UI improvements and bug fixes
Also, we reached over 42,000 users! Thanks for the support! 🎉🎉🎉
I think @github may be lying to me. I recently set up a small organisation. We have no need (nor budget) for Copilot Business and yet I’ve received a notification that one member of the organisation has requested it. There’s no way to see who. I checked with the members and it does not appear to have come from any of them. Is this #GitHub spamming me? Has anyone else had this and felt suspicious?
First part of a new long term home project coming in. An #Ubiquiti PoE+ switch to power a small #Kubernetes cluster built using #raspberrypi nodes. Going to blog about every step once it has been completed. But it is going to be a few quarters long project doing bit by bit
Did a small but significant upgrade to the temporary #kubernetes node autoscaler. It will now turn on as many nodes as there are pending pods (whichever is lowest). This will save me from waiting up to 6 minutes before all nodes are online to handle #GitHub Actions workflows. And #talos boot timing is pretty consistent. Those were all turned in within a second of each other: