Ben Grande 383c840f2f doc: lint markdown files ... Only way to have a unified markdown syntax is to enforce the wanted syntax by linting the files. Don't rely on the many markdown syntaxes, be consistent.		2024-07-04 17:27:31 +02:00
..
markdown-lint.sh	doc: lint markdown files	2024-07-04 17:27:31 +02:00
pgp-expiration.sh	feat: build and sign RPM packages	2024-06-12 14:44:04 +02:00
qubesbuilder-gen.sh	ci: set spec vendor as git user.name is unset	2024-06-22 12:39:51 +02:00
release.sh	feat: build and sign RPM packages	2024-06-12 14:44:04 +02:00
requires-program.sh	build: quiet build and verbose changelog	2024-06-13 14:03:16 +02:00
salt-fix.sh	refactor: initial commit	2023-11-13 14:33:28 +00:00
salt-lint.sh	doc: lint markdown files	2024-07-04 17:27:31 +02:00
setup.sh	chore: copyright update	2024-01-29 16:49:54 +01:00
shell-lint.sh	refactor: initial commit	2023-11-13 14:33:28 +00:00
spec-build.sh	fix: build RPM contained in spec definitions	2024-06-24 08:24:48 +02:00
spec-gen.sh	doc: lint markdown files	2024-07-04 17:27:31 +02:00
spec-get.sh	doc: lint markdown files	2024-07-04 17:27:31 +02:00
toc-gen.sh	refactor: initial commit	2023-11-13 14:33:28 +00:00
unicode-prohibit.sh	feat: print hex of unicode	2024-03-14 12:09:49 +01:00
yumrepo-gen.sh	build: quiet build and verbose changelog	2024-06-13 14:03:16 +02:00