Prevent fork PRs from failing the tests job on workshop coverage publish

[Copilot]

The tests job was failing after successful test execution because the workshop coverage publishing step attempted to write back to GitHub from a forked pull_request run. In that context, GITHUB_TOKEN lacks the required permissions and orgoro/coverage exits with Resource not accessible by integration.

• Root cause

  • The failure was not in Java/Go/Python/Node test execution.
  • The failing step was Publish Coverage for workshop, which runs orgoro/coverage@v3.2 and requires write-capable GitHub API access.

• Workflow change

  • Added a guard so the coverage publish step runs only when:
    • the event is not pull_request, or
    • the pull request originates from the same repository
  • Fork PRs still run the actual tests and coverage generation; they only skip the write-back step that cannot succeed with restricted credentials.

• Effect

  • Keeps coverage publication for trusted/internal contexts.
  • Prevents false-negative CI failures on external contributor PRs.

- name: Publish Coverage for workshop
  uses: orgoro/coverage@v3.2
  if: github.event_name != 'pull_request' || github.event.pull_request.head.repo.full_name == github.repository
  with:
    coverageFile: services/workshop/coverage.xml
    token: ${{ secrets.GITHUB_TOKEN }}

[github-actions]

Test Results

98 tests   98 ✅  2s ⏱️
18 suites   0 💤
 8 files     0 ❌

Results for commit f8fe62b.

[github-actions]

☂️ Python Coverage

current status: ✅

Overall Coverage

Lines	Covered	Coverage	Threshold	Status
1363	1089	80%	0%	🟢

New Files

No new covered files...

Modified Files

No covered modified files...

updated for commit: f8fe62b by action🐍