Rework the `check-fixers` CI job to use a matrix for the command

Open Beginner friendly
  • Is something wrong?
#2,457 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
70/100
Issue type
Refactor
Clarity
Mostly clear
Activity status
Active
Tech stack
github-actions
Domain
ci-cd

Research direction

Start with the check-fixers job in ci.yml and the same job in weekly.yml, and compare them with the static-code-analysis job in ci.yml, which already uses a matrix for its command. Rewrite both check-fixers jobs to use a matrix in the same way, keeping the job name unchanged. Done when both workflows pass with a matrix that still runs the existing fixer check, and the job names are unchanged.

Written by the indexing model from the issue text.

Description

github_actions

Story

As a developer, I want the check-fixers CI job to be prepared for adding another checker so that I can also check the checkStatic runTests.sh script.

Acceptance criteria

  • The check-fixers CI job in ci.yml uses a matrix for the command (similar to the static-code-analysis) job.
  • The check-fixers CI job in weekly.yml uses a matrix for the command (similar to the static-code-analysis) job.
  • The job still has its old name.
Dominant language
PHP
Stars
92
Forks
34
Avg merge
15h 28m
Merged PRs (30d)
64

Getting set up

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 TYPO3BestPractices/tea

All issues in TYPO3BestPractices/tea

Similar issues

More PHP issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.