If it's not obvious what this does (read the source): if uncrustify exists, it runs uncrustify on every C + header file in the repository. if yapf exists (or any of its variant names), it runs yapf on every python (py, py.in) file.
Both of these tools apply our coding standards (yapf will be less relevant for most people but should be installed nevertheless if you plan to write or edit python files (tests, mostly)). ng0 transcribed 714 bytes: > Hi, > > as suggested in naming to me, you can now run > > make pretty > > after a re-bootstrap and/or configure when uncrustify is detected and > subsequentially if yapf is detected. > > The nesting is not perfect, but for now it works. > > This should make the previous "pre-commit" file obsolete, I've moved it > to contrib for now. > > > The server side git hook is coming soon^TM. > > _______________________________________________ > GNUnet-developers mailing list > [email protected] > https://lists.gnu.org/mailman/listinfo/gnunet-developers _______________________________________________ GNUnet-developers mailing list [email protected] https://lists.gnu.org/mailman/listinfo/gnunet-developers
