I couldn't find the source on GitHub, but somebody has helpfully scraped them a few hours ago: https://github.com/pascalandy/dotfiles/blob/main/docs/refere...

I have a small CLI script that runs JQL `text ~ "$1"` (with per-repo filters on project/component).

I don't have to switch to the browser most of the time!

So in the trolley problem, you would abstain from supporting either side? I think that's actually a choice of supporting the status quo.

You are entitled to your opinion that I'm supporting the status quo by refusing to support the abject murder and depravity of one group of people over another, who may be slightly less murderous and depraved, and I'm entitled to my opinion that you are complicit in the the murder and depravity of the people you support.

I was there when the SDET role was eliminated.

Our team of 8 SDE and 5 SDET became a team of 8 devs who also owned tons of QA frameworks. It was awful, except each tiny we deleted a test suite for not being valuable; that was awesome!

If the Azure org was flooded with senior engineers who did not have senior-level experience architecting production software... That explains a lot.

My work was careful to explain: if you associate your personal GitHub account with their work org copilot, then they are the ones who manage copilot.

If you wouldn't use your personal email account on your work computer, I don't see why you wouldn't create a new GitHub account only for work.

There have been instances where GitHub has banned users for using an email address from a custom domain. If your account is associated with an enterprise plan the chances of that happening decrease significantly. Also puts you in much better position for recourse

Not private repos.

Now, anything that gets referenced in a copilot chat is fair game

Seems to acknowledge that windows 11 launched without expected features from 10.

Maybe they thought they could get away without taskbar location customisation, but now they have to put that complexity back in.

There's a CLI tool that writes the agent skills into the right folder. The other option would be to have everybody manually unzip a download into a folder which they might not remember.

Jenkins CI has a clever feature where every password it injects will be redacted if printed to stdout; `enveil run` could do that with the wrapped process?

Of course that's only a defense against accidents. Nothing prevents encoding base64 or piping to disk.

This is kind of backwards .

GitHub's privacy statement [1] says > GitHub personnel does not access private repository information without your consent except as provided...

Do you have any evidence that private repos on GitHub are being used for training?

In the opposite case, if you have a public repo on GitHub then you should expect it to be laundered through LLMs :\

[1] https://docs.github.com/en/site-policy/privacy-policies/gith...