WordPress / WordPress/phpunit-test-runner

Process all commits

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

Nobody has claimed this yet.

  • #212 by @javiercasares — closed without merging
ContributorDay enhancement hackathon
Dominant language
PHP
Stars
77
Forks
77
Avg merge
15d 15h
Merged PRs (30d)
4

Description

Currently, the Runner gets the latest WordPress version and processes that last commit. That means that not every different commit is processed and sent to the Reporter.

We may find a way to save the list of all commits (for example, in the last 24 hours), save them in a JSON file with the date, commit ID and whether it's processed or not, and start running until it last all? Or maybe one in every execution.

When the information is sent to the “reporter”, there is a revision value, so we can send all the revisions and not only the latest.

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.

Research direction

Start by tracing how the Runner obtains the latest WordPress version and selects its last commit, then inspect how revisions are sent to the Reporter. The issue mentions tracking commits in a dated JSON file with processed status, but leaves the execution strategy open. Done should mean every relevant commit is processed and its revision is sent to the Reporter.

Written by the indexing model from the issue text.

Assessment

Tech stack
php
Domain
tooling
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.