Write logic to generate project structure

[nchaloult]

If we use Github's API to traverse the project structure of a public repo, one of the things that we get back are absolute paths to each file in the repo as strings. Given a list of these file path strings, we need to generate Markdown with a "tree printout," similar to that of the tree command.

If we recognize the name and placement of a particular directory, we should include a comment about what that directory is for in this printout. For instance, if we find a src/ directory at the root of the repo, we should include a statement about how source files live there, as opposed to other types of files in the repo.

[nchaloult]

I've written a first draft of some functionality.

What Works

• We can parse a response body from the Github API, ripping out the absolute paths of all directories in a repo e778235cf8b7cca93cba9dc0e0d697012a1b33cd
• We can generate a tree-like printout of that directory structure 86da0ac3b5bdaec1b8c15d96d53b3c14dbdd76d8

What Isn't Ready

• We aren't including comments about, or short descriptions of, commonly existing directories that we should be able to infer details about
  • i.e., if we see a src/ directory at the root of a repo, we can infer that source files live there, as opposed to other types of files in the repo
• We aren't taking advantage of any fancy markdown features yet
  • No relative links to each folder in the repo