Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Test CI is failing for external contributors

Open
#47 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
github-actions, python
Domain
ci-cd, security

Research direction

Start by reading the existing test CI workflow and the linked GitHub Security Lab article, then inspect how external pull requests handle secrets and the coverage.xml artifact. Confirm the two-workflow approach in a test external-contributor scenario. Done means test CI remains safe and coverage.xml is published successfully for external contributors.

Written by the indexing model from the issue text.

Description

bug

Currently, test CI is using the pull_request trigger. However, with this trigger the secrets are not populated when the PR author is external to the repository.

This is done on purpose for security reasons: https://securitylab.github.com/resources/github-actions-preventing-pwn-requests/

Many persons on the internet suggest to use pull_request_target, but according to a rapid oversight of github securitylab article, this is only a workaround with does not help with security at all.

The proper solution seems to separate the workflow in two:

  • existing workflow will only publish the coverage.xml as an artifact
  • a new workflow will be responsible to publish this coverage.xml

Seems pretty simple to implement, but to be confirmed (I skimmed through github article way too fast) and tested of course.

Dominant language
Python
Stars
1
Forks
2
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from openzim/_python-bootstrap

All issues in openzim/_python-bootstrap

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.