Gallopsled/pwntools

Switch to coveralls github action instead of running commands manually

Open

#2480 opened on Oct 2, 2024

View on GitHub
 (0 comments) (0 reactions) (0 assignees)Python (11,127 stars) (1,684 forks)batch import
featuregood first issuetesting

Description

We should consider using https://github.com/marketplace/actions/coveralls-github-action#complete-parallel-job-example instead of our own solution. That would have avoided the hidden-files problem when combining the coverage data manually.

Contributor guide

Tech stack
pythongithub actions
Domain
devopsci cd
Issue type
refactor
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
GitHub Actions basicsYAML syntax
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70
Research direction
Examine the current coverage reporting workflow in .github/workflows (likely a YAML file). Compare the manual commands with the Coveralls GitHub Action example provided. Propose a pull request that replaces the manual steps with the action, ensuring parallel jobs and coverage collection are handled correctly.