Fix typo in README.md and fix CI from forks

.github/workflows/docker.yml

@@ -50,7 +50,9 @@ jobs:
             src/technologies/convince/task_2_solution/
           docker compose run test bash -c "source /delib_ws/install/setup.bash && pytest /delib_ws/src/dependencies/convince/AS2FM/test"
           docker compose down --remove-orphans
-      - name: Push to gh registry with sha and branch name
+      - name: Push to gh registry with sha and branch
+        # Do not push on PRs from forks.
+        if: ${{ !github.event.pull_request.head.repo.fork }}
         run: |
           echo ${{ secrets.GITHUB_TOKEN }} | docker login ghcr.io -u ${{ github.repository_owner }} --password-stdin
           # tag with sha and push
@@ -72,6 +74,8 @@ jobs:
         run: |
           docker save ${{ env.REGISTRY_IMAGE }}:${{ env.TAG_NAME }} | gzip > ./roscon_delib_ws_2024.tar.gz
       - name: Release
+        # Do not release on PRs from forks.
+        if: ${{ !github.event.pull_request.head.repo.fork }}
         uses: ncipollo/release-action@v1
         with:
           artifacts: './roscon_delib_ws_2024.tar.gz'

.github/workflows/lint.yml

@@ -3,7 +3,6 @@ on:
   push:
     branches: [main]
   pull_request:
-    branches: [main]
 
 jobs:
   pre-commit:

README.md

@@ -118,7 +118,7 @@ It will ask you for your `sudo` password.
 ### Develop inside the container using VSCode
 
 If you want to develop inside the container using VSCode, you need to have the [Docker extension](https://marketplace.visualstudio.com/items?itemName=ms-azuretools.vscode-docker) installed.
-To see option "Attach Visual Studio Code" you also need to download VS Code extenstion Dev Containers.
+To see the option "Attach Visual Studio Code", you also need to download the [Dev Containers extension](https://marketplace.visualstudio.com/items?itemName=ms-vscode-remote.remote-containers).
 
 Attach to the container as shown in the image below: