Minor fix to README formatting#61
Conversation
derobins
requested review from
gaoikawa,
jordan-turbofish,
kurtmcmillan and
riley-dixon
as code owners
There was a problem hiding this comment.
Pull Request Overview
This PR improves the formatting consistency in README.md by wrapping the Git branch name "hipFile" with backticks to format it as inline code. This is a standard markdown convention for technical identifiers like branch names.
- Adds backticks around "hipFile" branch references in two locations
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| We've created a fork of [ROCm/HIPIFY](https://github.com/ROCm/HIPIFY) at | ||
| [derobins/HIPIFY](https://github.com/derobins/HIPIFY). Changes to support | ||
| hipFile can be found in the hipFile branch. Please note that this branch | ||
| hipFile can be found in the `hipFile` branch. Please note that this branch |
There was a problem hiding this comment.
[nitpick] The word 'hipFile' at the beginning of this line (referring to the technology) should remain unformatted, but consider consistency: if branch names use backticks, the project name 'hipFile' in line 20 and 'libhipfile' in line 27 create inconsistency. However, the current change correctly formats only the branch name reference 'hipFile branch', which is appropriate. The technology reference 'hipFile' at the start is correctly left without backticks.
No description provided.