Added screenshots except 1

Author: saritai

assets/images/help/repository/code-scanning-affected-branches.png

@@ -31,7 +31,11 @@ Each alert highlights a problem with the code and the name of the tool that iden
 {% data reusables.code-scanning.alert-default-branch %}
 {% 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)
+{% else %}
+![Example alert from {% data variables.product.prodname_code_scanning %}](/assets/images/help/repository/code-scanning-alert-old.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-alert-description.png

@@ -39,7 +39,11 @@ You can use more than one issue to track the same {% data variables.product.prod
 
 - A "tracked in" section will also show in the corresponding alert page. 
 
+  {% ifversion fpt or ghec or ghes > 3.4 or ghae-issue-6249 %}
+  ![Tracked in section on code scanning alert page](/assets/images/help/repository/code-scanning-alert-tracked-in-section.png)
+  {% else %}
   ![Tracked in section on code scanning alert page](/assets/images/help/repository/code-scanning-alert-tracked-in-pill.png)
+  {% endif %}
 
 - On the tracking issue, {% data variables.product.prodname_dotcom %} displays a security badge icon in the task list and on the hovercard. 
 
@@ -65,7 +69,11 @@ The status of the tracked alert won't change if you change the checkbox state of
 1. Optionally, to find the alert to track, you can use the free-text search or the drop-down menus to filter and locate the alert. For more information, see "[Managing code scanning alerts for your repository](/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/managing-code-scanning-alerts-for-your-repository#filtering-code-scanning-alerts)."
 {% 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)
+   {% else %}
    ![Create a tracking issue for the code scanning alert](/assets/images/help/repository/code-scanning-create-issue-for-alert.png)
+   {% endif %}
    {% data variables.product.prodname_dotcom %} automatically creates an issue to track the alert and adds the alert as a task list item.
    {% data variables.product.prodname_dotcom %} prepopulates the issue:
    - The title contains the name of the {% data variables.product.prodname_code_scanning %} alert.

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

@@ -1 +1 @@
-The status and information on the alert page only reflects the state of the alert on the default branch of the repository, even if the alert exists in other branches. You can see the status of the alert on non-default branches in the **Affected branches** section on the right-hand side of the alert page. If an alert doesn't exist in the default branch, the status of the alert will display as "in pull request" or "in branch" and will be colored grey.
+The status and details on the alert page only reflect the state of the alert on the default branch of the repository, even if the alert exists in other branches. You can see the status of the alert on non-default branches in the **Affected branches** section on the right-hand side of the alert page. If an alert doesn't exist in the default branch, the status of the alert will display as "in pull request" or "in branch" and will be colored grey.