Potential fix for code scanning alert no. 1: Workflow does not contain permissions

[JerwinPRO]

Potential fix for https://github.com/JerwinPRO/SlideshowGallery/security/code-scanning/1

In general, the problem is fixed by adding an explicit permissions block to the workflow (at the root or per-job level) that restricts the GITHUB_TOKEN to the minimum needed scopes. For a simple CI workflow that just checks out the code and runs builds/tests, contents: read is sufficient.

The best minimal fix here, without changing existing functionality, is to add a workflow-level permissions block just below the name: Swift line. This will apply to the build job (and any future jobs that don’t override it) and set the GITHUB_TOKEN to read-only on repository contents. No other permissions (like pull-requests or issues) are required by the current steps. No imports or additional files are needed; this is a pure YAML change in .github/workflows/swift.yml.

Specifically:

• Edit .github/workflows/swift.yml.
• Insert:

  permissions:
    contents: read

  between the existing name: Swift line and the on: block.
  This preserves all existing behavior while constraining token permissions to the least privilege required.

Suggested fixes powered by Copilot Autofix. Review carefully before merging.