ctrf-io / ctrf-io/github-test-reporter
Filtering when using a merge queue
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 376
- Forks
- 42
- PR merge metrics
- No merged PRs in 30d
Description
We are using a github merge queue to merge changes into our main branch and run the tests. Unfortunately the previous reports are filtered out of our history. The Action is producing the following output:
⏮️ Processing previous results
Starting workflow runs processing...
Reached maximum limit (4 pages, 400 workflow runs)
Baseline 1 is out of range. Available previous reports: 0
Successfully processed 1 reports from 400 workflow runs
The branches used by the github merge queue are always in the form like this: origin/gh-readonly-queue/main/pr-<pr-id>-<id>. We do not run the tests on the main branch, because they are already executed in the merge queue. Is it possible to configure the filtering to include the merge queue runs?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the Action's workflow runs processing and the filtering that reports the merge queue branches. Check how branches named origin/gh-readonly-queue/main/pr-- are handled and define done as including their previous reports instead of reporting no available history.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, typescript
- Domain
- ci-cd, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100