Gollum VS Guard

That seems something in the ballpark of my favorite wiki software:

https://github.com/gollum/gollum

Edit and view pages as a normal markdown wiki. But the backend is just a git repository of markdown files so you can also just use your text editor and git pull/push. Usable by any novice but with the ideal power user interface.

I'm currently using Gollum Wiki in this way. It reads from a git repository, formats the markdown files nicely, and has a limited editor that is useful in a pinch.

I use Gollum, it's very simple but fits my needs.

Gollum would be an excellent solution. It's a web interface to a directory of markdown (or other formats), backed by git. Easy to sync the plain text files on your own devices (e.g. Syncthing) while still having a public web interface for school/work computers.

Gollum could meet the need. Logseq might work as well; here's a potential guide to self-hosting.

Maybe gollum it’s markdown based

I use ikiwiki, but I have also seen gollum mentioned here.

Gollum might be something worth looking into. It is basically a clone of the GitHub Wiki pages, built on top of git (so it uses version-controlled flat files as backend).

Gollum wiki fits the description, with git and a satisfying look and feel to boot.

Guard is a Ruby gem that can be used to run test cases automatically when source files change. For example, with guard-minitestand a simple Guardfile, you can run tests as the files are modified.

Text and file processing. Everything from parsing log files and generating reports, to watching folders with the Guard library and doing things with the files.

Perhaps using guard you can automate that https://github.com/guard/guard

It seems like where you are, devs are pushing code that fails in the CI/CD pipeline, which means, if your test suite isn't flakey, they aren't running tests locally. I had this problem too. I work on a rails monorepo, so I use the guard gem to automatically run certain tests when certain files are changed. There should be an analagous tool in whatever language/framework env(s) you're working in.

Check out https://github.com/guard/guard and https://github.com/guard/guard-rspec (if you're using rspec)

Installation guide for guard

Guard is a gem I have some prior experience with; it can be configured so that when a change is made to a file (for example: models/user.rb) it will autorun the associated test file (in this example: user_test.rb). As you can imagine, this significantly cuts down on the time until seeing either red or green tests which is super helpful for TDD and a necessary first part of TCR.

Now, consider this a mea culpa, as I know there are many ways this could go wrong. The guard documentation was also kind enough to warn me as such. This is, for better or for worse, my first attempt at building out a way to TCR in Rails. I’m excited to be able to follow up as I spend more time with my monstrous guardfile and this workflow so I can let you know how it goes.

Two key pieces of guard documentation, one on creating an inline guard and the other on hooks and callbacks. All of the docs were very helpful though!