ssc meta info

.gitignore

@@ -73,15 +73,9 @@
 
 
 #######################
-# Include some additional file formats in any output folder. You might have
-# to change the name of the Output folder to whatever it is called in your
-# project, but we strongly recommend that you only include these files in
-# a subset of the folders where you are certain no private data is ever stored.
-!/**/Output/**/*.txt
-!/**/Output/**/*.csv
-!/**/Output/**/*.xml
-!/**/Output/**/*.eps
-!/**/Output/**/*.svg
+# Some admin data in txt formet
+!/**/admin/**/*.txt
+
 
 #######################
 # Include all the files with passwords or tokens here. All files named
@@ -94,8 +88,3 @@ passwords.*
 password/
 passwords/
 .Rproj.user
-
-
-
-
-

admin/ssc-meta-info.txt

@@ -0,0 +1,16 @@
+
+TITLE:
+'STATA_LINTER': tool to detect and correct bad Stata coding practices
+
+DESCRIPTION
+
+The stata_linter package provides linter for Stata code. Read about what a linter is here: https://en.wikipedia.org/wiki/Lint_(software). This linter is based on the best practices outlines in The DIME Analytics Coding Guide published as an appendix to the book Development Research in Practice. See here https://worldbank.github.io/dime-data-handbook/coding.html. For more info about this linter, see https://github.com/worldbank/stata_linter.
+
+AUTHOR:
+"DIME Analytics, DIME, The World Bank Group", dimeanalytics@worldbank.org
+
+KEYWORDS:
+"linter", "style guide", "code best practices"
+
+STATA VERSION REQUIREMENT:
+Stata 16