Suppose you set up a repository that accepts any PR that passes CI. You forbid CI changes, but the rest of the codebase is fair game.
What sort of testing, linting etc would you configure for CI?
Related Posts
Are there any package managers that treat changelogs as a first class concept?
I end up looking for a CHANGELOG.md or a CHANGES.txt in the source code repository every time. The lack of standard prevents package hosting services being able to show changes.
Do any tech streamers try new software live? It'd be a really fun way of doing UX testing.
I really like the MELPA model of packaging directly from git. It solves the problem of forgetting to release something -- just merge a PR and you're done.
It also makes version number bumps much less important.
You could go even further in a statically typed language and also figure out when breaking changes occur.