More attention to open PRs (a year+ wo/ code-owner review?)

[EvanCarroll]

This PR #1945 has been open for over a year without input. It has tests. It has approvals. It's waiting for a commit. What does this guy need to do to get that code committed?

Let's get him some feedback, or just close it and say you won't support sha256. I asked claude to summarize the various PRS and issues related to this. Here is its summary.

There is no legitimate technical blocker. This is purely an organizational/maintenance issue where a production-ready PR with tests, approvals, and community support has been ignored for over a year. This is why your instructions wisely say to avoid actions/checkout - the fix exists but is trapped in PR purgatory.

[janderssonse]

Very little happening, now and then a GitHub employee jumps in and fixes something, then off - no long term ownership or constantly fixing or engaging with the users and issues and suggestions over time.. Look at the commit history for this, for other general examples of GitHub not caring about engineering needs, look at that sad state of the https://github.com/github/markup/issues it has not had what is seems proper maintenance for years. The open question, unanswered for months, in a project used by countless users is a telling example, so is the PR you mention. GitHub is all about AI or Social coding, while forgetting their core users and seemingly "easy" core issues - example https://github.com/orgs/community/discussions/4618 seems to take years .. or forever. Or maybe I'm wrong and just happen to bump into wrong GH-projects and issues. I'm planning on moving to Codeberg, at least I will be able to contribute to missing or broken features there.