update workflows

Author: nir-valtman

.github/stale.yml

@@ -2,7 +2,7 @@
 # Stalebot configuration file.
 # https://github.com/probot/stale
 #
-# Derived from https://github.com/returntocorp/semgrep/blob/cfe5b63516f3e91d0687093ae6b4a6c6f07e63cf/.github/stale.yml
+# Derived from https://github.com/opengrep/opengrep/blob/cfe5b63516f3e91d0687093ae6b4a6c6f07e63cf/.github/stale.yml
 #
 # We use stalebot as follows:
 # - it reminds us to prioritize issues that don't have a priority:* label

.github/workflows/num-rules.yml

@@ -1,4 +1,4 @@
-name: semgrep-rules-test-historical
+name: opengrep-rules-test-historical
 on:
   pull_request:
     branches:
@@ -15,7 +15,7 @@ jobs:
     steps:
     - uses: actions/checkout@v2
       with:
-        path: semgrep-rules
+        path: opengrep-rules
         fetch-depth: 0
     - uses: actions/setup-python@v2
       with:
@@ -24,32 +24,33 @@ jobs:
       id: changed-files
       uses: tj-actions/changed-files@v41
       with:
-        path: semgrep-rules
+        path: opengrep-rules
         separator: ","
     # need to delete these directories or else we get linter errors during 
     # the "validate" step.
+    # TODO: deploy a pip for opengrep
     - name: install semgrep
       run: pip3 install semgrep
     - name: delete stats directory
-      run: rm -rf semgrep-rules/stats
+      run: rm -rf opengrep-rules/stats
     - name: delete rules requiring Semgrep Pro
-      run: rm -rf semgrep-rules/apex semgrep-rules/elixir
+      run: rm -rf opengrep-rules/apex opengrep-rules/elixir
     # TODO: remove this in the future, there was a regression in semgrep that
     # caused non-rule YAML files to be validated
     - name: delete YAML files that are not rules
       run: |
-        rm -f semgrep-rules/.pre-commit-config.yaml
-        rm -rf semgrep-rules/.github
+        rm -f opengrep-rules/.pre-commit-config.yaml
+        rm -rf opengrep-rules/.github
     - name: grab historical semgrep version
       env:
         GH_TOKEN: ${{ github.token }}
-      run: semgrep-rules/scripts/historical-semgrep-version
+      run: opengrep-rules/scripts/historical-semgrep-version
     - name: validate rules on historical semgrep version
       run: |
-        docker run --rm -v ${GITHUB_WORKSPACE}/semgrep-rules:/src returntocorp/semgrep:${SEMGREP_OLD_VERSION} semgrep --validate --config /src
+        docker run --rm -v ${GITHUB_WORKSPACE}/opengrep-rules:/src opengrep/opengrep:${SEMGREP_OLD_VERSION} semgrep --validate --config /src
     - name: test with historical semgrep version
       run: |
-        TESTSUITE_OUTPUT="$(docker run --rm -v ${GITHUB_WORKSPACE}/semgrep-rules:/src returntocorp/semgrep:${SEMGREP_OLD_VERSION} semgrep --test --test-ignore-todo /src || true)"
+        TESTSUITE_OUTPUT="$(docker run --rm -v ${GITHUB_WORKSPACE}/opengrep-rules:/src opengrep/opengrep:${SEMGREP_OLD_VERSION} semgrep --test --test-ignore-todo /src || true)"
         echo "=== Testsuite output ==="
         echo "${TESTSUITE_OUTPUT}"
         echo "========================"
@@ -69,7 +70,7 @@ jobs:
           done
         fi
         if (( ${#PR_FAILURES[@]} != 0 )) ; then
-          echo "The following test(s) failed with Semgrep v${SEMGREP_OLD_VERSION} are caused by this PR:"
+          echo "The following test(s) failed with Opengrep v${SEMGREP_OLD_VERSION} are caused by this PR:"
           for i in "${PR_FAILURES[@]}" ; do
             echo $i
           done

.github/workflows/semgrep-rules-test-historical.yml

@@ -28,7 +28,7 @@ You can also learn how to write rules using the [interactive, example-based Semg
 
 ## Contributing
 
-We welcome Semgrep rule contributions directly to this repository! When submitting your contribution to this repository, we’ll ask you to make Semgrep, Inc. a joint owner of your contributions. While you still own copyright rights to your rule, joint ownership allows Semgrep, Inc. to license these contributions to other [Semgrep Registry](https://semgrep.dev/r) users pursuant to the LGPL 2.1 under the [Commons Clause](https://commonsclause.com/). See full [license details](https://github.com/returntocorp/semgrep-rules/blob/develop/LICENSE).
+We welcome Semgrep rule contributions directly to this repository! When submitting your contribution to this repository, we’ll ask you to make Semgrep, Inc. a joint owner of your contributions. While you still own copyright rights to your rule, joint ownership allows Semgrep, Inc. to license these contributions to other [Semgrep Registry](https://semgrep.dev/r) users pursuant to the LGPL 2.1 under the [Commons Clause](https://commonsclause.com/). See full [license details](https://github.com/opengrep/opengrep-rules/blob/develop/LICENSE).
 
 Note: To contribute, review the **[Contributing to Semgrep rules](https://semgrep.dev/docs/contributing/contributing-to-semgrep-rules-repository/)** documentation.
 
@@ -42,7 +42,7 @@ Join [Slack](https://go.semgrep.dev/slack) for the fastest answers to your quest
 
 ### GitHub action to run tests
 
-If you fork this repository or create your own, you can add a GitHub Action to your workflow that will automatically test your rules using the latest version of Semgrep. See our [semgrep-rules-test example](https://github.com/returntocorp/semgrep-rules/blob/develop/.github/workflows/semgrep-rules-test.yml).
+If you fork this repository or create your own, you can add a GitHub Action to your workflow that will automatically test your rules using the latest version of Semgrep. See our [semgrep-rules-test example](https://github.com/opengrep/opengrep-rules/blob/develop/.github/workflows/semgrep-rules-test.yml).
 
 ### Rulesets