| Age | Commit message (Collapse) | Author |
|---|
|
* I just realized that repository specific commit feeds are already provided by both CGit and GitHub
** i.e. I made the mistake of not checking if my current system already provides the required functionality when I wanted to aggregate my commits and found this to be a use case for StaticXSLT
* feeds are fetched via `curl`
** this will be a local request in production
** the messages are still cleaned using `sed` and transformed into _XHTML_ using `peg-markdown`
* instead of reading a customized Git log output CommitLog now simply transforms CGit ATOM feeds using identity templates
** this requires ATOM namespace removal which is implemented in `utility/remove_namespace.xsl`
|
|
* moved repository feeds to `repository` directory
* replaced paginated XHTML timeline target with and ATOM feed
** removed `paginated_timeline.xsl` transformation including the `04_meta` level
** removed CSS and master stylesheets
* added title, url and commit count meta data to `meta.xml`
* expanded ATOM feed URLs
* timeline feed has an upper limit of `commit_count` items
** repository feeds have the same limit because only `commit_count` commits of every repository are fetched in the first place
|
|
|
|
* added CSS style based on my personal blog
** modified master and stream templates accordingly
* added date-time, repository name and commit hash output
* removed single-repository log export as it is not the purpose of this application
|
|
* another application based on StaticXSLT
* git is instructed to export XML through a special log format definition
* the commit messages are processed as Markdown
* currently implemented result views are commits-by-repo and a paginated timeline of all commits in every repository
* repositories to be read have to be defined in the `repositories.xml` file in the `00_content` level
|
