mv source-code article to new directory

Author: Paul Osinski

…integrations/source-code-repositories.md …ements_tests/source-code-repositories.mddocs/content/en/open_source/archived_docs/integrations/source-code-repositories.md renamed to docs/content/en/working_with_findings/organizing_engagements_tests/source-code-repositories.md docs/content/en/open_source/archived_docs/integrations/source-code-repositories.md renamed to docs/content/en/working_with_findings/organizing_engagements_tests/source-code-repositories.md

@@ -1,17 +1,18 @@
 ---
-title: "Source code repositories"
+title: "Link Findings to source code"
 description: "Integration of repositories to navigate to the locaction of findings in the source code."
 draft: false
 weight: 5
 ---
 
-Findings can have a filepath and a line number as the location of the vulnerability. This is typically set when scanning an application with a Static Application Security Test (SAST) tool. If the repository of the source code is specified in the Engagement, DefectDojo will present the filepath as a link and the user can navigate directly to the location of the vulnerability.
+Certain tools (particularly SAST tools) will include the associated file name and line number in vulnerability data. If the repository of the source code is specified in the Engagement, DefectDojo will present the filepath as a link and the user can navigate directly to the location of the vulnerability.
 
 ## Setting the repository in the Engagement and Test
 
 ### Engagement
 While editing the Engagement, users can set the URL of the specific SCM repo. 
-For Interactive Engagement it needs to be the URL including the branch:
+
+For an Interactive Engagement, it needs to be a URL that specifies the branch:
 - for GitHub - like https://github.com/DefectDojo/django-DefectDojo/tree/dev
 ![Edit Engagement (GitHub)](images/source-code-repositories_1.png)
 - for GitLab - like https://gitlab.com/gitlab-org/gitlab/-/tree/master
@@ -21,13 +22,13 @@ For Interactive Engagement it needs to be the URL including the branch:
 - for standalone/onpremise BitBucket https://bb.example.com/scm/some-project/some-repo.git or https://bb.example.com/scm/some-user-name/some-repo.git for user public repo (like git clone url)
 ![Edit Engagement (Bitbucket standalone)](images/source-code-repositories-bitbucket-onpremise_1.png)
 
-For CI/CD Engagement, where user could set commit hash, branch/tag and code line it should look like examples below:
-- for GitHub - like https://github.com/DefectDojo/django-DefectDojo 
-- for GitLab - like https://gitlab.com/gitlab-org/gitlab
-- for public BitBucket, Gitea and Codeberg - like https://bitbucket.org/some-user/some-project.git (like git clone url)
-- for standalone/onpremise BitBucket https://bb.example.com/scm/some-project.git or https://bb.example.com/scm/some-user-name/some-repo.git for user public repo (like git clone url)
+For CI/CD Engagements, the commit hash, branch/tag and code line can vary, so you only need to include the URL of the repository.
+- for GitHub - like `https://github.com/DefectDojo/django-DefectDojo`
+- for GitLab - like `https://gitlab.com/gitlab-org/gitlab`
+- for public BitBucket, Gitea and Codeberg - like `https://bitbucket.org/some-user/some-project.git` (like git clone url)
+- for standalone/onpremise BitBucket `https://bb.example.com/scm/some-project.git` or `https://bb.example.com/scm/some-user-name/some-repo.git` for user public repo (like git clone url)
 
-If user does not set commit hash or branch/tag in appropriate fields of CI/CD Engagement edit form, the URL should look like in Interactive Engagement edit form.
+In a CI/CD Engagement, you can specify a commit hash or branch/tag in the **Edit Engagement** form, which will be appended to any links rendered by DefectDojo.  If these are not set, the SCM URL will need to contain a complete link which includes the code branch. 
 
 SCM navigation URL is composed from Repo URL using SCM Type. A specific SCM type can be set in Product custom field "scm-type". If no "scm-type" is set and the URL contains "https://github.com", a "github" SCM type is assumed.
 
@@ -42,7 +43,7 @@ Product SCM type add:
 Possible SCM types could be 'github', 'gitlab', 'bitbucket', 'bitbucket-standalone', 'gitea', 'codeberg' or nothing (for default github).
 
 
-## Link in Finding
+## Source code Links in Findings
 
 When viewing a finding, the location will be presented as a link, if the repository of the source code has been set in the Engagement: