…ple commits per Atom feed entry
The parser doesn't quite work. I've hacked it up to at least get the revision hash correct, but that's a hack. (Currently it just searches the whole log message for "/commit/[hex stuff]", but it should get the revision link first and then parse the hash from that instead.) Three things are still needed for this parser to work correctly: * Needs to parse the link to the revision from the log content. * Needs to parse the commit message from the log content. * Would be nice if it could identify the file(s) changed, either directly from the log content (if it's included) or by scraping the revision page (like googlecode does). This isn't a requirement, but it's a nice feature. I've also added a test (using the parrot-plumage repo) to allow development of the parser.
* When you "push" a tree with more than one entry causing a merge in the server, the resulting new entries aren't all at the top of the change tree. Swap out the timestamp-comparison for a seen-cache, so we can emit any entry we haven't seen before, regardless of whether it's new or not. Update the documentation accordingly. * Add handling for newly created and removed files (+/-), rather than just looking for the modified ones ("m"). This will fix some skipped commits.
…ell. Flatten the hyphen to an underscore. Give github the same fix, just in case. The standalone test.pl script didn't like that the module name didn't match the project name, fix that too.
… githubparser doesn't need to.