You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using the "comment" function in octopus-gihub v0.4, comments are incorrectly being added to the PR description instead of being submitted as issue comments. This behavior is inconsistent with expected functionality and disrupts the review workflow.
Click the "comment" button provided by octopus-gihub. Write a comment and submit it.
Expected Outcome:
The comment should appear in the comment section of the PR, maintaining the PR description unaltered.
Actual Outcome:
The comment is being added to the PR description, modifying the original content of the description.
Proposed Fix:
The issue can be resolved by modifying const url = window.location.href; to const url = window.location.pathname;. This change correctly gets the path of the PR URL, not including the query string or fragment.
The text was updated successfully, but these errors were encountered:
Issue:
When using the "comment" function in octopus-gihub v0.4, comments are incorrectly being added to the PR description instead of being submitted as issue comments. This behavior is inconsistent with expected functionality and disrupts the review workflow.
Steps to Reproduce:
Navigate to a specific PR link (e.g. *: add instruction for editing config pingcap/docs#13666 (review))
Click the "comment" button provided by octopus-gihub. Write a comment and submit it.
Expected Outcome:
The comment should appear in the comment section of the PR, maintaining the PR description unaltered.
Actual Outcome:
The comment is being added to the PR description, modifying the original content of the description.
Proposed Fix:
The issue can be resolved by modifying
const url = window.location.href;
toconst url = window.location.pathname;
. This change correctly gets the path of the PR URL, not including the query string or fragment.The text was updated successfully, but these errors were encountered: