Ewoud Kohl van Wijngaarden
Ewoud Kohl van Wijngaarden
> Yes that is a reasonable thing to do, actually, should not be necessary. I vaguely remember there is a loop and they upload facts every N minutes. There is...
My idea comes to have something like `guides/index.adoc` in every branch and then somehow gather all of those when building the website. That way the index lives very close to...
Something I thought about was taking more of the tabs approach, but no idea if it's actually feasible/usable. Basically have a header that's `Foreman $version` and then 3 big tabs:...
> Current version ("Version x.y") stays selected in the version dropdown at all times so you don't need to remember it. Which gives you easy access to your preferred version...
@aneta-petrova I should have mentioned that we're currently in the middle of branching (https://community.theforeman.org/t/foreman-3-15-branching-process/43138) and I'd like to get that wrapped up first. Especially since you'd touch those files here.
https://github.com/theforeman/foreman-documentation/pull/3915 implements a compromise.
Version 8.2.1 is no longer supported. It is resolved in #1566 so you'll need to update to at least 10.0.3.
I recall there was a rubocop-rspec plugin that looked for these wrong filenames. > Easiest solution is declare the types private api and remove the tests but I'm not sure...
Is this a duplicate of https://github.com/puppetlabs/puppetlabs-postgresql/issues/1560?
We merged #1540