Use CI to improve the quality of emacs distribution

I've been using https://github.com/leotaku/elisp-check for a couple of years, and pretty happy with it, almost no changes needed to my use-package based one config (I had to comment a couple of packages, though).

Nix overlay for Emacs. Straight for package freezing. Using rolling versions without some form of locking is guaranteed to result in non-reproducibility issues and instability. Nix and cachix both have Github actions. I'm working on a repo to demonstrate this integration.

Thanks for the heads up. The article you mentioned is very interesting. Looks we are using same APIs. The focus of my article is to make the solution scalable. So I wrote more code to process false alarms raised by 3rd party packages. Emacs distribution (spacemacs, doomemacs, prelude, emacs.d ...) need handle hundreds of (sometimes thounsands of ) 3rd party packages. That's the problem I try to solve.

> So I wrote more code to process false alarms raised by 3rd party packages. I think fixing the packages is a better idea

As my article said, some packages use macro to create anonymous functions. Tt's hard to locate root cause of warnings. Most compiling warnings are harmless. Package is still working. Besides, a emacs distribution could use hundreds of packages. I use three hundred packages, it takes too much time to contact every package's maintainer. The reason to ignore 3rd party package warnings is to make sure to improve my code's quality so it doesnt raise warning/error.

> I use three hundred packages The fun thing is I used about 200 (130 external ones), and only two caused critical errors while checking.