On Thu, 1 May 2025 at 10:20, sebb <seb...@gmail.com> wrote: > > On Thu, 1 May 2025 at 09:55, Niall Pemberton <niall.pember...@gmail.com> > wrote: > > > > On Thu, 1 May 2025 at 09:29, sebb <seb...@gmail.com> wrote: > > > > > retire.py currently uses Python, but Jekyll is based on Ruby, so I > > > have so far been working on a replacement in Ruby. Does it matter what > > > language is used? > > > > > > Can this be incorporated into the Jekyll site? I believe you can create > > custom “commands” - so maybe possible, like running the Jekyll build > > locally, also be able to execute command(s) that replicate the puthon > > functionality. > > It would be possible to create an on-demand workflow that prompts for > the project id. > That can then run the script and generate a new/updated project.yaml > file in a new branch. > The workflow can then create a PR from the branch. > > I have tested all the parts separately, but have yet to put them together.
I've added a sample workflow It's still a work in progress ... > > From my PoV this would be better since I have Jekyll & Ruby installed - but > > I’ve never used Python. > > > > Having said that, I run Jekyll in WSL (windows Linux) which I only recently > > started using - so could probably also work out python > > Unless the script needs modification, the language is largely > irrelevant so long as it is installed. > Sounds like staying with Ruby would involve less work. > > > Niall > > > > > > > > > > > > Sebb > > >
