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.

Sign up for GitHub

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

PR comment: GH logic was backwards #2032

Merged
merged 1 commit into from
Mar 18, 2025
Merged

PR comment: GH logic was backwards #2032

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions docs/semgrep-code/triage-remediation.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -139,7 +139,7 @@ To **reopen multiple findings** in the **No grouping** view, follow these steps:

## Triage findings through PR and MR comments

Triage your Semgrep AppSec Platform findings displayed as comments in GitHub PRs and GitLab MRs by replying with another comment.
Triage your Semgrep AppSec Platform findings displayed as comments in PRs and MRs by replying with another comment.

<Tabs
defaultValue="gh"
Expand Down Expand Up @@ -202,7 +202,7 @@ Triaging a finding as **Ignored** through a comment in Bitbucket changes the sta
<TabItem value='gh'>

### Prerequisites
- A **private** GitHub Free or Team cloud-hosted repository. This feature is not enabled for public GitHub repositories or GitHub Enterprise public and private repositories.
- A **private** GitHub Free or Team cloud-hosted repository or GitHub Enterprise repository. This feature is not enabled for public GitHub Cloud repositories.
- You have completed a [Semgrep core deployment](/deployment/core-deployment).

### Enable triage through GitHub PR comments:
Expand Down