Add concise macOS troubleshooting notes for common install/runtime issues. #221
Conversation
… (Tesseract, Poppler, Pixi warnings, SyntaxWarning, first-run output)
… commit deletion of legacy install-troubleshoot
Bumps [docker/build-push-action](https://github.com/docker/build-push-action) from 5.0.0 to 6.18.0. - [Release notes](https://github.com/docker/build-push-action/releases) - [Commits](docker/build-push-action@0565240...2634353) --- updated-dependencies: - dependency-name: docker/build-push-action dependency-version: 6.18.0 dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
castelao
left a comment
There was a problem hiding this comment.
@bpulluta , thanks for doing this. I have a question. What is your vision on how these troubleshooting notes will overlap with GitHub issues? I can see both working together, but I'm thinking on how to leave a clear intention. If someone finds a bug on the installation process or instructions, we want they to open an issue for us to fix, or luckily they would open directly a PR improving the documentation or installation process. Do you agree?
I think the documentation don't need to keep the history on the origins of the issue, but a direct and clear instructions on how to avoid the problem such as " on OSX install with home brew first ...", and we leave to track the history through the archived issues. What are your thoughts?
Related to that, would you have any suggestion on how to improve the templates for new issues?
|
Will fix linter errors in a separate PR and merge it shortly |
Files changed
docs/installation-troubleshooting/*(Tesseract, Poppler build/runtime, Pixi warnings, SyntaxWarning, first-run note)Notes