Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bad usage of backticks in warning message #79

Closed
CasperWA opened this issue Nov 17, 2022 · 3 comments · Fixed by #80
Closed

Bad usage of backticks in warning message #79

CasperWA opened this issue Nov 17, 2022 · 3 comments · Fixed by #80
Assignees
Labels
bug Something isn't working

Comments

@CasperWA
Copy link
Collaborator

As seen in this workflow run, the use of backticks (`) in the warning message results in some bad print outs.

@CasperWA CasperWA added the bug Something isn't working label Nov 17, 2022
@CasperWA CasperWA self-assigned this Nov 17, 2022
@jesper-friis
Copy link
Contributor

jesper-friis commented Nov 17, 2022

I am not sure I understand this issue correctly.

But backtics are a standard way to highlight variables in documentation. If the documentation system if it doesn't allow backtics in warning messages, I will say it is a bug in the documentation system rather than in the warning message.

@CasperWA
Copy link
Collaborator Author

This specifically regards a GitHub Actions-specific warning message here: https://github.com/SINTEF/ci-cd/blob/main/.github/workflows/ci_tests.yml#L364
It is simply the bash interpreter that thinks it needs to run a command due to the backticks. It is a very minor issue. This has nothing to do with the documentation system. Please take more care to investigate.

@CasperWA CasperWA changed the title Bad usage og backticks in warning message Bad usage of backticks in warning message Nov 17, 2022
@CasperWA
Copy link
Collaborator Author

See the GitHub documentation for more information.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants