matomo-org / matomo-org/matomo-for-wordpress

Do not require manual command runs as part of updating core

Open
#910 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
PHP
Stars
145
Forks
35
Avg merge
2d 2h
Merged PRs (30d)
6

Description

Instead of having update-core.sh require developers to manually run two commands and have the repo include generated/minified assets, store all non-test core matomo files in this repo and have the commands be run as part of the automated release process.

e2e tests, when they are added, should run these commands as well before running tests.

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 with update-core.sh and trace how core Matomo files and generated/minified assets are currently handled. Then inspect the automated release process and determine how the existing commands can run there, with future e2e tests using the same step; done means developers no longer run them manually.

Written by the indexing model from the issue text.

Assessment

Tech stack
bash, php, wordpress
Domain
build-system, release
Issue type
Refactor
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.