aboutsummaryrefslogtreecommitdiff
path: root/README
diff options
context:
space:
mode:
authorB. Watson <urchlay@slackware.uk>2023-02-04 05:02:52 -0500
committerB. Watson <urchlay@slackware.uk>2023-02-04 05:02:52 -0500
commit880b34b30b46c0e7e2264d9227f88a2488a476e5 (patch)
tree6c563dd0e43308993358f8d02fa738d95cdbf8e0 /README
parent69c42c3c353b262cf2c79ce18773b7ff74e95bb5 (diff)
downloadsbo-maintainer-tools-880b34b30b46c0e7e2264d9227f88a2488a476e5.tar.gz
sbofixinfo: mention in README and QUICKSTART.
Diffstat (limited to 'README')
-rw-r--r--README9
1 files changed, 6 insertions, 3 deletions
diff --git a/README b/README
index 08dcffa..7ef3fab 100644
--- a/README
+++ b/README
@@ -17,6 +17,8 @@ Included tools:
- pre-commit-sbolint: a git pre-commit hook you should use, that
automatically calls sbolint and stops you from committing bad code.
+- sbofixinfo: attempts to automatically fix common .info file problems.
+
Note that the SBo admins use these tools as part of the approval
process, when you submit an update. Failure to pass the lint checks
is a valid reason for rejecting your submission, so you should either
@@ -66,6 +68,7 @@ admins and explain the situation; it may mean sbolint needs updating.
Documentation:
--------------
-For more information, see the sbolint and sbopkglint man pages (or
-run the scripts with --doc; it's the same thing). There's also a
-QUICKSTART file that gives the bare minimum info to get started.
+For more information, see the sbolint, sbopkglint, and sbofixinfo man
+pages (or run the scripts with --doc; it's the same thing). There's
+also a QUICKSTART file that gives the bare minimum info to get
+started.