Pulling GitHub into the kernel process

Posted Jul 26, 2021 16:22 UTC (Mon) by mathstuf (subscriber, #69389)
In reply to: Pulling GitHub into the kernel process by tpo
Parent article: Pulling GitHub into the kernel process

Alas, there isn't a fancy webpage for it (it's used internally and the code is public, but no "marketing" behind it). Feel free to email me about any questions you might have (email address is in the history) or we can discuss here.

The way we deploy it is here: https://gitlab.kitware.com/utils/ghostflow-director/ (as a webhook handler for gitlab and github) and the core routines (including a nascent cli tool) are here: https://gitlab.kitware.com/utils/rust-ghostflow

Pulling GitHub into the kernel process

Posted Jul 27, 2021 9:35 UTC (Tue) by tpo (subscriber, #25713) [Link] (1 responses)

> Feel free to email me about any questions you might have (email address is in the history) or we can discuss here.

The Repo https://gitlab.kitware.com/utils/rust-ghostflow doesn't have a README.md and it's description is: "Routines which implement various parts of "ghostflow", or the git-hosted workflow.", which basically says "foo implements foo", which isn't helpful to the reader's understanding of what *actually* the purpose of that software is.

So I suggest to link from the description of https://gitlab.kitware.com/utils/rust-ghostflow to https://gitlab.kitware.com/utils/ghostflow-director/, which has minimal info on what ghostflow is, or even better to add a README.md to https://gitlab.kitware.com/utils/rust-ghostflow with minimal info that at least contains that link.

Pulling GitHub into the kernel process

Posted Jul 27, 2021 15:04 UTC (Tue) by mathstuf (subscriber, #69389) [Link]

Thanks. I'll try and carve out some time to spruce up the descriptions and such.