renaming images

Author: saritai

assets/images/help/repository/code-scanning-alert-new.png renamed to assets/images/help/repository/code-scanning-alert-page.png

@@ -32,9 +32,9 @@ Each alert highlights a problem with the code and the name of the tool that iden
 {% endif %}
 
 {% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-6249 %}
-![Example alert from {% data variables.product.prodname_code_scanning %}](/assets/images/help/repository/code-scanning-alert.png)
+![Example alert from {% data variables.product.prodname_code_scanning %}](/assets/images/help/repository/code-scanning-alert-page.png)
 {% else %}
-![Example alert from {% data variables.product.prodname_code_scanning %}](/assets/images/help/repository/code-scanning-alert-old.png)
+![Example alert from {% data variables.product.prodname_code_scanning %}](/assets/images/help/repository/code-scanning-alert.png)
 {% endif %}
 
 If you set up {% data variables.product.prodname_code_scanning %} using {% data variables.product.prodname_codeql %}, you can also find data-flow problems in your code. Data-flow analysis finds potential security issues in code, such as: using data insecurely, passing dangerous arguments to functions, and leaking sensitive information.

assets/images/help/repository/code-scanning-create-issue-for-alert-new.png renamed to assets/images/help/repository/code-scanning-create-issue-for-alert-button.png

@@ -48,10 +48,14 @@ By default, the code scanning alerts page is filtered to show alerts for the def
 {% endif %}
 {% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-6249 %}
      {% data reusables.code-scanning.alert-default-branch %}
-   <!-- Insert screenshot with status and Affected branches sections highlighted-->{% endif %}
+     ![The "Affected branches" section in an alert](/assets/images/help/repository/code-scanning-affected-branches.png){% endif %}
 1. Optionally, if the alert highlights a problem with data flow, click **Show paths** to display the path from the data source to the sink where it's used.
+  {% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-6249 %}
+   ![The "Show paths" link on an alert](/assets/images/help/repository/code-scanning-show-paths-link.png)
+   {% else %}
    ![The "Show paths" link on an alert](/assets/images/help/repository/code-scanning-show-paths.png)
-1. Alerts from {% data variables.product.prodname_codeql %} analysis include a description of the problem. Click **Show more** for guidance on how to fix your code.
+   {% endif %}
+2. Alerts from {% data variables.product.prodname_codeql %} analysis include a description of the problem. Click **Show more** for guidance on how to fix your code.
    ![Details for an alert](/assets/images/help/repository/code-scanning-alert-details.png)
 
 For more information, see "[About {% data variables.product.prodname_code_scanning %} alerts](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts)."

assets/images/help/repository/code-scanning-show-paths-new.png renamed to assets/images/help/repository/code-scanning-show-paths-link.png

@@ -70,7 +70,7 @@ The status of the tracked alert won't change if you change the checkbox state of
 {% endif %}
 1. Towards the top of the page, on the right side, click **Create issue**. 
    {% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-6249 %}
-   ![Create a tracking issue for the code scanning alert](/assets/images/help/repository/code-scanning-create-issue-for-alert-new.png)
+   ![Create a tracking issue for the code scanning alert](/assets/images/help/repository/code-scanning-create-issue-for-alert-button.png)
    {% else %}
    ![Create a tracking issue for the code scanning alert](/assets/images/help/repository/code-scanning-create-issue-for-alert.png)
    {% endif %}

content/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning-alerts.md

@@ -80,8 +80,11 @@ To see more information about an alert, users with write permission can click th
 
 In the detailed view for an alert, some {% data variables.product.prodname_code_scanning %} tools, like {% data variables.product.prodname_codeql %} analysis, also include a description of the problem and a **Show more** link for guidance on how to fix your code.
 
+{% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-6249 %}
+![Alert description and link to show more information](/assets/images/help/repository/code-scanning-alert-description.png)
+{% else %}
 ![Alert description and link to show more information](/assets/images/help/repository/code-scanning-pr-alert.png)
-
+{% endif %}
 ## Fixing an alert on your pull request
 
 Anyone with push access to a pull request can fix a {% data variables.product.prodname_code_scanning %} alert that's identified on that pull request. If you commit changes to the pull request this triggers a new run of the pull request checks. If your changes fix the problem, the alert is closed and the annotation removed.