Emelia Smith

I think this should now be improved, there'll still be a redirect flow between PodBrowser and your IdP on first load, but it usually remember that you granted access.

Closing this as fixed, as further reports have not been filed.

Added comments to try to keep this in sync, since we can't reuse the tool-versions file in GitHub Actions directly

@ClearlyClaire the main reason I ended up using asdf for Hugo was because I contribute to multiple Hugo sites each running different incompatible versions, so I'd constantly get weird breakages...

I'd be of the inclination to suggest we do adopt `.tool-versions` here, not necessarily to say adopt asdf, but rather to have a file in the root of the repository...

> Also, its too bad the format here with extended doesnt quite match the format needed in the CI config... Yeah, that annoys me too, but there isn't really anything...

@mjankowski an alternative way to do this is to actually parse the tool-versions file for the CI pipeline: ```yaml - name: Setup Hugo Version id: hugo_version run: | HUGO_VERSION=$(cat .tool-versions...

It'd probably actually be possible to write a small go program to convert from tool-versions to the environment variables: https://github.com/asdf-vm/asdf/blob/master/internal/toolversions/toolversions.go

But yeah, it's just an annoying thing that actions-hugo splits the `extended` out of the version.

Anyway, it's a relatively simple improvement that could be done to the hugo action: https://github.com/peaceiris/actions-hugo/issues/670