Programmers Stack Exchange is a question and answer site for professional programmers interested in conceptual questions about software development. It's 100% free.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

What information would you expect to see in the github README?

Should everything go in the README? i.e.

  • Introduction

  • Installation

  • Versions

  • User Guide

  • Implementation

  • Testing

  • Related Resources

Or should you just put certain things in the README (Introduction, Installation, Versions) and the other information is best placed in the Github wiki?

share|improve this question
I would put licence terms also – py_script Jun 24 '13 at 15:45
In overly general terms, there should be enough information to tell me whether the project is useful to me if all I know about it is the name. Don't assume anything about how the reader found it. – Keith Thompson Jun 24 '13 at 15:48
This question has a very detailed/good answer here: – Rodrigo Graça Oct 6 '14 at 13:32

I expect to see an introduction and brief overview. There should be something there to convince me that the project solves a particular problem. After reading the README, I should know enough information to know what the project does, what it requires, how to build it, and how to use it. That information doesn't all need to be in the README, but links to that information should be.

share|improve this answer
+1 for brief. Don't say "README" and then put a bunch of garbage in that doesn't need to be read. – Korey Hinton Jun 24 '13 at 16:22

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.