Fix GitHub release repository context

[IsmailM]

Summary

The v0.0.2 workflow successfully published to PyPI, but its final GitHub release job failed because that job does not check out the repository. As a result, gh release create could not infer which repository to target.

Pass GITHUB_REPOSITORY explicitly through the --repo option. This keeps the release job checkout-free while allowing future tag releases to create their GitHub release and attach the validated distributions.

The v0.0.2 GitHub release was created manually from the exact workflow artifacts, and their SHA-256 hashes match the files published to PyPI.

Validation

• Release workflow YAML parsed successfully
• Ruff formatting and lint checks passed
• Dependency audit passed
• Verified gh release create --repo eye2gene/PyeScan against v0.0.2

[Copilot]

Pull request overview

Fixes the GitHub release step in the tag-based release workflow by explicitly setting the target repository for gh release create, allowing the github-release job to remain checkout-free while still creating/releases and attaching built distributions.

Changes:

• Update gh release create invocation to include --repo "${GITHUB_REPOSITORY}".
• Convert the release command to a folded multi-line YAML run: >- for readability while preserving the same shell command.

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.