Page MenuHomePhabricator

Add a more complete README for GitHub
ClosedPublic

Authored by chad on Jan 28 2015, 8:36 PM.
Tags
None
Referenced Files
F19227467: D11542.id27782.diff
Fri, Dec 19, 4:58 AM
F19098191: D11542.id27776.diff
Dec 4 2025, 4:00 PM
F19098190: D11542.id27782.diff
Dec 4 2025, 4:00 PM
F19098189: D11542.id27780.diff
Dec 4 2025, 4:00 PM
F18819831: D11542.id27780.diff
Oct 22 2025, 10:07 AM
F18813929: D11542.id27782.diff
Oct 20 2025, 8:06 PM
F18766165: D11542.diff
Oct 7 2025, 3:17 PM
F18756662: D11542.id27776.diff
Oct 5 2025, 12:32 PM
Subscribers

Details

Reviewers
epriestley
btrahan
Commits
Restricted Diffusion Commit
rP4d6aea7ce81a: Add a more complete README for GitHub
Summary

Not sure this is entirely correct or needed as a separate file, but I think GitHub's README could use some additonal information

Test Plan

Used a Markdown editor

Diff Detail

Repository
rP Phabricator
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

chad retitled this revision from to Add a more complete README for GitHub.
chad updated this object.
chad edited the test plan for this revision. (Show Details)
chad added reviewers: epriestley, btrahan.

Isn't this exactly the same as the existing README?

I mean, it's a beautiful document, I'm just not sure we need two of them.

chad edited edge metadata.
  • derpy derpy

Let's just remove README? We should parse all this stuff pretty much the same way in Remarkup nowadays.

My main question is, do we need two documents? Can these just be one, somehow?

Ok, that's what I thought just wasn't sure.

epriestley edited edge metadata.
This revision is now accepted and ready to land.Jan 28 2015, 8:48 PM
This revision was automatically updated to reflect the committed changes.