2025-11-17T06:55:16Zhttps://repos.tuckerm.useleventy-plugin-repoviewer contributorsTucker McKnight <tucker@pangolin.lan>2025-11-17T06:55:16Zhttps://repos.tuckerm.us/repos/eleventy-plugin-repoviewer/branch/data-type-changes/commits/8eaecc836900be5206cd8a1fb9e9db43c799112fremove the generic operations class, just go with git operationsTucker McKnight <tucker@pangolin.lan>2025-11-16T09:11:29Zhttps://repos.tuckerm.us/repos/eleventy-plugin-repoviewer/branch/data-type-changes/commits/fb82fedb228595143547ae3003ba3426a5e39bc9More implementation of the new type The new commit field and branch heads work now, and other functions/filters/template pages work as expected with those new fields. Switch to the new Repository type is pretty much done now. Also did some miscellaneous things, like adding basic string types to some function arguments. Also started changing all uses of "patch" to "commit," which is a holdover from when this project started with darcs.Tucker McKnight <tucker@pangolin.lan>2025-11-16T08:50:11Zhttps://repos.tuckerm.us/repos/eleventy-plugin-repoviewer/branch/data-type-changes/commits/5dd869e68ccb84734c1a7dafe5d757709f1df124Remove typescript from frontend, go with plain JS The added `export {}` statement at the bottom makes it unuseable in browsers. Apparently the solution is to use webpack, which I'd rather not do. Not many typescript features were being used in the frontend anyway.Tucker McKnight <tucker@pangolin.lan>2025-11-10T07:16:21Zhttps://repos.tuckerm.us/repos/eleventy-plugin-repoviewer/branch/data-type-changes/commits/7e40e5b6c81b4a222015b3d5586bc53eebd258c5Switching some more things over to the new Repository type Also removed anything that prints out commits in order, as that needs to be re-thought for the new format. So I left some todos in there.Tucker McKnight <tucker@pangolin.lan>2025-11-03T06:25:42Zhttps://repos.tuckerm.us/repos/eleventy-plugin-repoviewer/branch/data-type-changes/commits/268685ca2b2d95435aef7ae0cae6328464f07903add more clear types for getBranchInfoTucker McKnight <tmcknight@instructure.com>2025-10-21T06:55:01Zhttps://repos.tuckerm.us/repos/eleventy-plugin-repoviewer/branch/data-type-changes/commits/bc3cc7d43bcc61ad8d76a89a4f5a1fc126de6776more type ideasTucker McKnight <tmcknight@instructure.com>2025-10-21T06:45:35Zhttps://repos.tuckerm.us/repos/eleventy-plugin-repoviewer/branch/data-type-changes/commits/929902548271025085c41d2271bccd17fdbd689frough draft of new repo data typeTucker McKnight <tucker@pangolin.lan>2025-10-12T08:23:44Zhttps://repos.tuckerm.us/repos/eleventy-plugin-repoviewer/branch/data-type-changes/commits/2376512fc3745b47f8cb9446f92c85d3fe25488bRemove darcs functionality :( I'd like to come back to darcs later, when I've come up with a way of making some kind of plugin system for making this work with multiple VCSes. In the meantime, development will be faster if I just focus on git.Tucker McKnight <tucker@pangolin.lan>2025-10-12T07:51:26Zhttps://repos.tuckerm.us/repos/eleventy-plugin-repoviewer/branch/data-type-changes/commits/a16d13fd4194c9b3bca1d2350a62f84c9a2d7fdcUse for..of loops instead of promises These wait for each other in a sequence, unliked a Promise.all(array.map), which executes everything all at once. Artifact steps whould be able to depend on the result of the previous one, so the need to go in sequence.Tucker McKnight <tucker@pangolin.lan>2025-10-12T07:51:02Zhttps://repos.tuckerm.us/repos/eleventy-plugin-repoviewer/branch/data-type-changes/commits/8627e8ba9f828cadbb067fe229b0a7fdf670e2d1add raw file template that I forgot earlierTucker McKnight <tucker@pangolin.lan>2025-10-12T04:49:07Zhttps://repos.tuckerm.us/repos/eleventy-plugin-repoviewer/branch/data-type-changes/commits/8559a132c4d0d70fe0d5ad2ae5d19749f0e8f3e2Add a "raw" file template, which shows the plain text of a file Add a link to said raw file when viewing the file in the Files tab. Also remove an unnecessary "async" from a filter that was not async. Also .gitignore the docs directory, which gets generated when `npm run build` is run.Tucker McKnight <tucker@pangolin.lan>2025-10-12T04:12:59Zhttps://repos.tuckerm.us/repos/eleventy-plugin-repoviewer/branch/data-type-changes/commits/005a065fd24cdf90fbf1e4d44df8672e9a929ebaAdd an optional "artifactSteps" category This field in the config allows you to specify a list of build steps. These build steps will run on every branch in the repo, then copy a directory into the resulting _site directory for that given branch.Tucker McKnight <tucker@pangolin.lan>2025-10-04T22:36:08Zhttps://repos.tuckerm.us/repos/eleventy-plugin-repoviewer/branch/data-type-changes/commits/645f473cf457475af466ea3301d01ed03339b3efAdd typedoc and add more specific build commandsTucker McKnight <tucker@pangolin.lan>2025-10-04T22:24:36Zhttps://repos.tuckerm.us/repos/eleventy-plugin-repoviewer/branch/data-type-changes/commits/458b461b7a067e38876ef8b9fe0d024d58526796Slugify top nav links The output filenames were already slugified, the links just needed to match.tucker <tucker@pangolin.lan>2025-09-29T06:15:29Zhttps://repos.tuckerm.us/repos/eleventy-plugin-repoviewer/branch/data-type-changes/commits/73413ac6fe72983cd8ecfce71c769cace73ef150tweak diff colortucker <tucker@pangolin.lan>2025-09-29T06:01:55Zhttps://repos.tuckerm.us/repos/eleventy-plugin-repoviewer/branch/data-type-changes/commits/2a0989f9bdb909ab012ed5a3616c4ef34f75aff0readme changestucker <tucker@pangolin.lan>2025-09-28T07:49:17Zhttps://repos.tuckerm.us/repos/eleventy-plugin-repoviewer/branch/data-type-changes/commits/b3ae7795e6d7d4f1b3634a3885563988761c5915fix git sha in package lock of example sitetucker <tucker@pangolin.lan>2025-09-28T07:48:33Zhttps://repos.tuckerm.us/repos/eleventy-plugin-repoviewer/branch/data-type-changes/commits/4bd0a4da949ba7c9c86ba4502ad30f9700751155fix URL in readmetucker <tucker@pangolin.lan>2025-09-28T07:34:23Zhttps://repos.tuckerm.us/repos/eleventy-plugin-repoviewer/branch/data-type-changes/commits/4c0630ec2a943d540dde8716e2a075a4a140d8b0Fix bug where date and author were not found in merge commits The line that starts with "merge" was not expected, and it threw off the line numbers that I was expecting before.tucker <tucker@pangolin.lan>2025-09-28T06:54:00Zhttps://repos.tuckerm.us/repos/eleventy-plugin-repoviewer/branch/data-type-changes/commits/49dee7e6a0042b336c34be2705f8bae811e20646fix href in main nav linktucker <tucker@pangolin.lan>2025-09-28T06:53:38Zhttps://repos.tuckerm.us/repos/eleventy-plugin-repoviewer/branch/data-type-changes/commits/048139a87ab559991c2a88bb45be7e96ed090598make example site reference remote URLtucker <tucker@pangolin.lan>2025-09-28T06:07:26Zhttps://repos.tuckerm.us/repos/eleventy-plugin-repoviewer/branch/data-type-changes/commits/29237ed0d328c1e2001db91cb2c48a2566e19c7callow path to be empty, placing generated site at the roottucker <tucker@pangolin.lan>2025-09-28T06:07:09Zhttps://repos.tuckerm.us/repos/eleventy-plugin-repoviewer/branch/data-type-changes/commits/ceddc6b7c1833a6474de92cc29dbd48cfbb41174rename plugin and add 11ty plugins to example siteTucker McKnight <tmcknight@instructure.com>2025-09-28T03:42:34Zhttps://repos.tuckerm.us/repos/eleventy-plugin-repoviewer/branch/data-type-changes/commits/2c5c836e743d55d318a00a0197bc6fd7a72a9496Include an example 11ty site that uses this pluginTucker McKnight <tmcknight@instructure.com>2025-09-28T03:42:12Zhttps://repos.tuckerm.us/repos/eleventy-plugin-repoviewer/branch/data-type-changes/commits/d7962f32cd609a884169ca23446ab539e90f7bf5Update gitignore to include things in example_siteTucker McKnight <tmcknight@instructure.com>2025-09-28T02:42:08Zhttps://repos.tuckerm.us/repos/eleventy-plugin-repoviewer/branch/data-type-changes/commits/3d2bce97c01a5a43175463c0b37e5d74c18813a2Skip things that can't be done if plugins are missing RSS feed creationg, syntax highlighting, and readme display rely on other 11ty plugins being installed in order for them to work. If those plugins are not installed, skip those parts of the site generation.Tucker McKnight <tmcknight@instructure.com>2025-09-28T02:39:30Zhttps://repos.tuckerm.us/repos/eleventy-plugin-repoviewer/branch/data-type-changes/commits/9598642633882b9dbd04273af663f280799500fdAllow relative paths to be used for repo location Previously, relative paths couldn't be used because it first `cd`s into the _site directory, and then tries to clone the site strait from the location that you give it for the repo. `process.cwd` is the directory of the current 11ty site, which should be the "base" location that the user is using for relative paths to their repositories. By putting the current directory before the repo location, we should get the full path to the repository.Tucker McKnight <tmcknight@instructure.com>2025-09-28T02:32:39Zhttps://repos.tuckerm.us/repos/eleventy-plugin-repoviewer/branch/data-type-changes/commits/e00effc988e32d2e4f8501586283a893dcb90ba9Show helpful errors of the repo configuration is wrong This is done by using ts-json-schema-generator to produce a JSON schema from the ReposConfiguration typescript type. This happens when you run `npm run build`. The resulting file is saved in schemas/ReposConfiguration.json; this file should be committed when it is modified. The resulting JSON schema is then used to look for errors in the reposConfiguration object that the user passes in when they use this plugin. Ajv is used for this schema validation. This change conveniently made me realize that I hadn't yet added the new `path` property to the ReposConfiguration type, so that is now in there. ts-json-schema-generator doesn't seem to be able to "find" your type definitions unless they are exported like `export type ReposConfiguration...`, so src/configTypes.ts is formatted like that now.Tucker McKnight <tmcknight@instructure.com>2025-09-28T01:56:51Zhttps://repos.tuckerm.us/repos/eleventy-plugin-repoviewer/branch/data-type-changes/commits/9aa969caa6d1835f7b3d65a1285d7698da8e31bbcouple of readme changesTucker McKnight <tucker.mcknight@gmail.com>2025-09-15T04:37:38Zhttps://repos.tuckerm.us/repos/eleventy-plugin-repoviewer/branch/data-type-changes/commits/dd0baf14f4340442d43412c24d94774faffd721etesting syntax highlightingTucker McKnight <tucker.mcknight@gmail.com>2025-09-14T04:38:51Zhttps://repos.tuckerm.us/repos/eleventy-plugin-repoviewer/branch/data-type-changes/commits/b0f62affcdbe79c5630797810401c5898b1069a9add a readmeTucker McKnight <tucker.mcknight@gmail.com>2025-09-13T23:14:30Zhttps://repos.tuckerm.us/repos/eleventy-plugin-repoviewer/branch/data-type-changes/commits/9b0897442f1c238e39d26380447278ad28e0a8a3Rename node module, remove unnecessary 11ty dependencyTucker McKnight <tucker.mcknight@gmail.com>2025-09-13T23:14:07Zhttps://repos.tuckerm.us/repos/eleventy-plugin-repoviewer/branch/data-type-changes/commits/b823f101b8d6130536949eeff7f7f611eeafaf8afix repo path in clone commandTucker McKnight <tucker.mcknight@gmail.com>2025-09-13T20:48:56Zhttps://repos.tuckerm.us/repos/eleventy-plugin-repoviewer/branch/data-type-changes/commits/a6363affa7e9d9baa49798f68865c26d6bf78580Fix some node module nonsense idk Also use import.meta.dirname instead of __dirname because that's what's available when using es modules.Tucker McKnight <tucker.mcknight@gmail.com>2025-09-01T21:20:11Zhttps://repos.tuckerm.us/repos/eleventy-plugin-repoviewer/branch/data-type-changes/commits/315ce614460a8431610417bb5abc2cab53c88a48add rss feed templateTucker McKnight <tucker.mcknight@gmail.com>2025-09-01T20:58:33Zhttps://repos.tuckerm.us/repos/eleventy-plugin-repoviewer/branch/data-type-changes/commits/7cb5f370d1d866ba3f3a052be4cc4de169fb4d2fmake main link use reposPathTucker McKnight <tucker.mcknight@gmail.com>2025-09-01T20:57:21Zhttps://repos.tuckerm.us/repos/eleventy-plugin-repoviewer/branch/data-type-changes/commits/dff32ab50879651513459ddd97e4daf16df57088make links on patch.njk page use reposPath variableTucker McKnight <tucker.mcknight@gmail.com>2025-09-01T20:51:28Zhttps://repos.tuckerm.us/repos/eleventy-plugin-repoviewer/branch/data-type-changes/commits/4ccb6eca9b4d6b4e497cc558eb73652a69989e4eAdd patch.njk page Fix some references to static files that weren't using the reposPath variable. Put main.css in the vendors folder, which should be renamed at some point, but for now it gets main.css into a dist/ location that can be used by the virutal templates. Change the way the light/dark theme switcher works; just replace "prism.css" or "prism_dark.css" instead of replacing the full path. This avoids having to know the reposPath variable in a JS file.Tucker McKnight <tucker.mcknight@gmail.com>2025-08-30T21:49:47Zhttps://repos.tuckerm.us/repos/eleventy-plugin-repoviewer/branch/data-type-changes/commits/c69df816cee2eb0e74eed142f43eaca6c730ce22BROKEN HERE, add patches template. Breaks getLocation somehow?Tucker McKnight <tucker.mcknight@gmail.com>2025-08-30T21:31:06Zhttps://repos.tuckerm.us/repos/eleventy-plugin-repoviewer/branch/data-type-changes/commits/7f84e677975fa5c05bcc85b460f7dceddfc65559add path config option, which is used to determine the resulting URLTucker McKnight <tucker.mcknight@gmail.com>2025-08-24T07:15:08Zhttps://repos.tuckerm.us/repos/eleventy-plugin-repoviewer/branch/data-type-changes/commits/79d4a6719b7cafb44aea60b1544f0de50c471a24make clone work, add static JS files for frontendTucker McKnight <tucker.mcknight@gmail.com>2025-08-23T23:21:02Zhttps://repos.tuckerm.us/repos/eleventy-plugin-repoviewer/branch/data-type-changes/commits/b8a3bbdc1113ccb3120a8e1b01dd674de289fe7dwip: moving from separate site repo to plugin