Rename component to sast

.gitlab-ci.yml

@@ -1,5 +1,5 @@
 include:
-  - component: gitlab.com/$CI_PROJECT_PATH/all-jobs@$CI_COMMIT_SHA
+  - component: gitlab.com/$CI_PROJECT_PATH/sast@$CI_COMMIT_SHA
 
 stages: [test, release]
 

README.md

@@ -12,7 +12,7 @@ keyword.
 
 ```yaml
 include:
-  - component: gitlab.com/gitlab-components/sast/all-jobs@<VERSION>
+  - component: gitlab.com/gitlab-components/sast/sast@<VERSION>
 ```
 
 where `<VERSION>` is the latest released tag or `main`.
@@ -21,7 +21,7 @@ If you are converting the configuration to use components and want to leverage t
 
 ```yaml
 include:
-  - component: gitlab.com/gitlab-components/sast/all-jobs@main
+  - component: gitlab.com/gitlab-components/sast/sast@main
     rules:
       - if: $SAST_DISABLED == "true" || $SAST_DISABLED == "1"
         when: never
@@ -45,3 +45,7 @@ This assumes `SAST_DISABLED` variable is already defined in `.gitlab-ci.yml` wit
 | `search_max_depth` | `4` | Defines how many directory levels the search for programming languages should span |
 | `run_kubesec_sast` | `"false"` | Set it to `"true"` to run `kubesec-sast` job  |
 | `include_experimental` | `"false"` | Set it to `"true"` to enable [experimental analyzers](https://docs.gitlab.com/ee/user/application_security/sast/#experimental-features) |
+
+## Contribute
+
+Please read about CI/CD components and best practices at: https://docs.gitlab.com/ee/ci/components