Always private
DuckDuckGo never tracks your searches.
Learn More
You can hide this reminder in Search Settings
All regions
Argentina
Australia
Austria
Belgium (fr)
Belgium (nl)
Brazil
Bulgaria
Canada (en)
Canada (fr)
Catalonia
Chile
China
Colombia
Croatia
Czech Republic
Denmark
Estonia
Finland
France
Germany
Greece
Hong Kong
Hungary
Iceland
India (en)
Indonesia (en)
Ireland
Israel (en)
Italy
Japan
Korea
Latvia
Lithuania
Malaysia (en)
Mexico
Netherlands
New Zealand
Norway
Pakistan (en)
Peru
Philippines (en)
Poland
Portugal
Romania
Russia
Saudi Arabia
Singapore
Slovakia
Slovenia
South Africa
Spain (ca)
Spain (es)
Sweden
Switzerland (de)
Switzerland (fr)
Taiwan
Thailand (en)
Turkey
Ukraine
United Kingdom
US (English)
US (Spanish)
Vietnam (en)
Safe search: moderate
Strict
Moderate
Off
Any time
Any time
Past day
Past week
Past month
Past year
  1. Standard Readme started with the issue originally posed by @maxogden over at feross/standard in this issue, about whether or not a tool to standardize readmes would be useful.A lot of that discussion ended up in zcei's standard-readme repository. While working on maintaining the IPFS repositories, I needed a way to standardize Readmes across that organization.
    • Issues 4

      Issues 4 - RichardLitt/standard-readme: A standard style for README files - GitHub

    • Pull requests

      Pull requests - RichardLitt/standard-readme: A standard style for README files - GitHub

    • Actions

      Actions - RichardLitt/standard-readme: A standard style for README files - GitHub

    • Security

      GitHub is where people build software. More than 100 million people use GitHub to discover, fork, and contribute to over 420 million projects.

    • Insights

      We would like to show you a description here but the site won't allow us.

    • Contributors 22

      We would like to show you a description here but the site won't allow us.

  2. A compliant README must satisfy all the requirements listed below. Note: Standard Readme is designed for open source libraries. Although it's historically made for Node and npm projects, it also applies to libraries in other languages and package managers.. Requirements:
  3. standard --fix is built into standard for maximum convenience. Most problems are fixable, but some errors (like forgetting to handle errors) must be fixed manually. To save you time, standard outputs the message "Run standard --fix to automatically fix some problems" when it detects problems that can be fixed automatically.
  4. en.wikipedia.org

    The expression "readme file" is also sometimes used generically, for other files with a similar purpose. [citation needed] For example, the source-code distributions of many free software packages (especially those following the Gnits Standards or those produced with GNU Autotools) include a standard set of readme files:
  5. Standard Readme started with the issue originally posed by @maxogden over at feross/standard in this issue, about whether or not a tool to standardize readmes would be useful. A lot of that discussion ended up in zcei's standard-readme repository. While working on maintaining the IPFS repositories, I needed a way to standardize Readmes across ...
  6. docs.github.com

    Headings. To create a heading, add one to six # symbols before your heading text. The number of # you use will determine the hierarchy level and typeface size of the heading. # A first-level heading ## A second-level heading ### A third-level heading. When you use two or more headings, GitHub automatically generates a table of contents that you can access by clicking within the file header.
  7. Can’t find what you’re looking for?

    Help us improve DuckDuckGo searches with your feedback

Custom date rangeX