Copilot commented on code in PR #3899: URL: https://github.com/apache/texera/pull/3899#discussion_r2429682348
########## .github/PULL_REQUEST_TEMPLATE: ########## @@ -0,0 +1,50 @@ +<!-- +Thanks for sending a pull request (PR)! Here are some tips for you: + 1. If this is your first time, please read our contributor guidelines: + [Contributing to Texera](https://github.com/apache/texera/blob/main/CONTRIBUTING.md) + 2. Ensure you have added or run the appropriate tests for your PR + 3. If the PR is working in progress, mark it a draft on GitHub. Review Comment: Grammatical correction: replace 'working in progress' with 'work in progress'. ```suggestion 3. If the PR is work in progress, mark it a draft on GitHub. ``` ########## .github/PULL_REQUEST_TEMPLATE: ########## @@ -0,0 +1,50 @@ +<!-- +Thanks for sending a pull request (PR)! Here are some tips for you: + 1. If this is your first time, please read our contributor guidelines: + [Contributing to Texera](https://github.com/apache/texera/blob/main/CONTRIBUTING.md) + 2. Ensure you have added or run the appropriate tests for your PR + 3. If the PR is working in progress, mark it a draft on GitHub. + 4. Please write your PR title to summarize what this PR proposes, we + are following Conventional Commits style for PR titles as well. + 5. Be sure to keep the PR description updated to reflect all changes. +--> + +### What changes were proposed in this PR? +<!-- +Please clarify what changes you are proposing. The purpose of this section +is to outline the changes. + 1. If you propose a new API, clarify the use case for a new API. + 2. If you fix a bug, you can clarify why it is a bug. + 3. Please consider writing useful notes for better and faster reviews. +--> + + +### Any related issues, documentations, discussions? +<!-- +Please use this section to link other resources if not mentioned already. + 1. If this PR fixes an issue, please include `Fixes #1234`, `Resolves #1234` + or `Closes #1234`. If it is only related, simiply mention the issue number. Review Comment: Correct the misspelling 'simiply' to 'simply'. ```suggestion or `Closes #1234`. If it is only related, simply mention the issue number. ``` ########## .github/PULL_REQUEST_TEMPLATE: ########## @@ -0,0 +1,50 @@ +<!-- +Thanks for sending a pull request (PR)! Here are some tips for you: + 1. If this is your first time, please read our contributor guidelines: + [Contributing to Texera](https://github.com/apache/texera/blob/main/CONTRIBUTING.md) + 2. Ensure you have added or run the appropriate tests for your PR + 3. If the PR is working in progress, mark it a draft on GitHub. + 4. Please write your PR title to summarize what this PR proposes, we + are following Conventional Commits style for PR titles as well. + 5. Be sure to keep the PR description updated to reflect all changes. +--> + +### What changes were proposed in this PR? +<!-- +Please clarify what changes you are proposing. The purpose of this section +is to outline the changes. + 1. If you propose a new API, clarify the use case for a new API. + 2. If you fix a bug, you can clarify why it is a bug. + 3. Please consider writing useful notes for better and faster reviews. +--> + + +### Any related issues, documentations, discussions? Review Comment: Use the uncountable form 'documentation' instead of 'documentations' in this heading. ```suggestion ### Any related issues, documentation, discussions? ``` -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
