Test for breaking changes in Gutenberg plugin _before_ they're released in Core

Open
#374 1 comment 3 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
45/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
graphql, php
Domain
ci-cd, testing-qa

Research direction

Start with test-plugin-nightly.yml and trace how the existing Core compatibility testing runs. Determine how the Gutenberg plugin can be included in that testing path, then verify that incompatibilities are flagged before Core releases so they can be addressed in advance.

Written by the indexing model from the issue text.

Description

While test-plugin-nightly.yml is an honest attempt, since most changes happen in the Gutenberg plugin and don't always get merged until late in the release cycle, we should be testing against that as well.

Flagging incompatibilities before they break the ecosystem gives us time to address them in an optimal way (vs an urgent patch/workaround) or even provide feedback upstream on changes.

With core major releases going on hiatus for a year, there will be even more gutenberg-plugin locked changes, and likely an increase of people using it instead of waiting 12 months for things to get merged into core.

Dominant language
PHP
Stars
149
Forks
16
No merged PRs in 30d

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.

More from wpengine/wp-graphql-content-blocks

All issues in wpengine/wp-graphql-content-blocks

Similar issues

More PHP issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.