How GNU Make is tested
lowlevelbits.org
lowlevelbits.org
So no unit tests at all. I think that unit tests work very well for pure functions, but their utility decreases the more side effects your code has. Also, unit tests usually just add confusion when the unit tested is really an internal implementation detail, rather than refering to some object in the application's or library's external domain model.
[1] https://github.com/holocm/holo/tree/master/test for the core parts
I'm just arguing vocabulary, though. There seems to be a spectrum, pure unit tests on one side, then integration tests, with Canaries way off to the other side.
There were a number of bugs in the 3.81 release that I assume they now have tests for, since 4.x has been rock solid. (Off the top of my head, if you made a certain shape in the dependency graph with .PHONY targets, then .DELETE_ON_ERROR stopped working)
It's not GitHub, it's Savannah, as just linked literally 2 lines below :
- changing repo's description
- changing repo's homepage URL
- changing default branch
- (un)protecting a branch
- editing an issue comment
- adding files to a release
- removing files from a release
- removing a release
- renaming repo
- removing repo
- logging out
Most of these could be probably scripted via API, but I'm lazy...
Still better than Bitbucket, which won't you even log in with JS disabled.
https://mikegerwitz.com/about/githubbub
jwilk's list below seems much more comprehensive.