avoid suggestion identifier

[harjotgill]

Summary by OpenAI

Release Notes:

• Documentation: Guidelines added for code suggestions in GitHub pull request reviews. Suggestions must be within fenced code blocks with appropriate language identifier and should not use the suggestion identifier. Markdown format is preferred for responses.

"Code review guidelines, clear as day,
Will help us all work better, hooray!"

[github-actions]

🤖 OpenAI

Thank you for letting me participate in the code review. I have reviewed the changes made to the action.yml file and provided a summary of my findings below.

The changes made to the action.yml file add guidelines for code suggestions in GitHub pull request reviews. The guidelines specify that suggestions must be within fenced code blocks with appropriate language identifier and should not use the suggestion identifier. Markdown format is preferred for responses.

Here is a table summarizing the changes made to each file:

File	Summary
action.yml	Guidelines added for code suggestions in GitHub pull request reviews. Suggestions must be within fenced code blocks with appropriate language identifier and should not use the suggestion identifier. Markdown format is preferred for responses.

Overall, the changes made to the action.yml file provide clear guidelines for code suggestions in GitHub pull request reviews, which will help ensure that suggestions are communicated effectively and efficiently.

---

Chat with 🤖 OpenAI Bot (@openai)

• Reply on review comments left by this bot to ask follow-up questions. A review comment is a comment on a diff or a file.
• Invite the bot into a review comment chain by tagging @openai in a reply.

---