Appearance
Tracking findings across pushes
Each push to a pull request starts a new review. EasyMerge shows you which findings are new, which came back and which are still open, so you do not have to read the same comment twice.
Badges on findings
On the review detail page, a finding can carry one of these badges:
| Badge | Meaning |
|---|---|
| New | Raised for the first time in this pull request |
| Reappeared | Raised before, gone for a while, and now back |
| No longer detected | Not raised by a newer review; shown when you look at an older version. This does not confirm a fix |
A finding with no badge was already raised in an earlier review. The header of the review shows how many findings are new and how many reappeared, for example 2 new and 1 reappeared.
Showing only new or reappeared findings
Select the 2 new count in the review header to show only the findings that are new in this review, or the 1 reappeared count to show only the ones that came back. The file list, the findings and the next/previous navigation all narrow to them, and files without a matching finding are hidden. Only one of the two counts can be selected at a time: selecting the other one switches to it.
These filters work together with the severity and file-name filters; a note under the file search says how many files the filters hide. Select the count again, or clear the filters, to show everything.
If someone on your team has dismissed a finding on GitHub, the finding also shows that decision, such as False positive or Resolved on GitHub. See Dismissing a finding from GitHub.
Finding status on the pull request
The summary comment on the pull request includes a Finding status section for the latest commit:
- Open: still raised. Each one links to its comment thread.
- No longer detected: not raised at that commit.
- Not verified: EasyMerge could not check it at that commit.
While the section is being prepared, it reads Finding status: checking….
When a run finds nothing new but earlier findings are still open, its review status reads No new issues · N still open instead of No issues found, on GitHub and in the dashboard. While EasyMerge is still checking the earlier findings, it reads No new findings in this run. See the review status.
No longer detected is not the same as fixed
"No longer detected" does not confirm a fix. Check the change yourself before you rely on it.
Repeated findings stay off GitHub
By default, a finding that was already commented on an earlier commit is not posted again. It still appears on the review detail page and in the counts.
To post every finding on every push instead, turn on Post duplicate findings to GitHub in Repository settings, or set comments.post_duplicates: true in the configuration file.
Dismissing a finding from GitHub
Reply in the finding's comment thread on GitHub with one of these commands, at the start of the reply and in lower case:
| Reply | Shown as | Effect |
|---|---|---|
/easymerge false_positive | False positive | Not posted to GitHub again |
/easymerge intentional | Intentional | Not posted to GitHub again |
/easymerge wont_fix | Won't fix | Not posted to GitHub again |
/easymerge fixed | Fixed | Marks it as fixed; it can be posted again if it comes back |
You can add a note after the command, for example /easymerge intentional — kept for backwards compatibility.
Resolving the thread on GitHub marks the finding Resolved on GitHub. Unresolving the thread clears the decision.
People with write access to the repository can use every command. The author of the pull request can use /easymerge fixed only.
A dismissed finding stays visible in EasyMerge.
Creating a GitHub Issue from a finding
To follow up on a finding outside the pull request, open a GitHub Issue for it:
- Open the latest completed review and find the finding.
- Select Create GitHub Issue.
- Edit the Title (up to 200 characters) and Description (up to 20,000 characters). The Preview next to the description shows how it will look on GitHub. The description ends with links to the pull request on GitHub and to the review in EasyMerge.
- Select Create GitHub Issue at the bottom of the dialog, or Cancel to close it without creating anything.
The finding then shows an Issue #42 button that opens the issue on GitHub; hover over it to see whether the issue is open or closed. Select Refresh issue to update its state, for example after it is closed on GitHub. If EasyMerge cannot read the state, the button adds State unknown and keeps the existing link.
Creating an issue needs Post review on GitHub to be on for the repository, and Issues enabled on the GitHub repository. If something prevents it, EasyMerge tells you why:
| Message | What to do |
|---|---|
| EasyMerge needs the Issues permission on GitHub. | An organization owner must approve the new permission; use the Accept GitHub permission link |
| An organization admin must enable GitHub publishing before creating an issue. | Turn on Post review on GitHub for the repository |
| Issues are disabled for this repository on GitHub. | Enable Issues in the repository's GitHub settings |
| This repository is archived on GitHub. | Unarchive the repository first |
| A selected finding already has a GitHub issue. | Use the existing issue |
| Issue creation could not be confirmed. Check GitHub before retrying. | Look for the issue on GitHub, then select Refresh issue |
If GitHub asks you to slow down, the dialog says how many seconds to wait before trying again.