Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Verify BC breakages on pull requests, by comparing PR against base branch #226

Merged
merged 9 commits into from
Jul 11, 2023

Conversation

boesing
Copy link
Member

@boesing boesing commented Jul 9, 2023

Q A
New Feature yes

Description

This PR continues the work of #126 while adapting some changes to reduce complexity:

  • reduces event handling and focusses on GITHUB_BASE_REF environment variable instead
  • introduces a new Tool type ToolRunningContainerDefaultPhpVersion which targets tools which are pre-installed within the CI container (such as roave-backward-compatibility-check), it provides @default via php job configuration and thus, the CI container won't change the PHP version which is the default by the moment of executing the container (needs Introduce roave/backward-compatibility-check and @default php version laminas-continuous-integration-action#158)
  • Provides a configuration flag backwardCompatibilityCheck to opt-in for the roave-backward-compatibility-check, with v2 of the CI pipeline, this flag might be changed to be enabled by-default and projects need to opt-out for it

@Xerkus @internalsystemerror I've added you guys as you gave feedback in the initial #126 PR.
@Ocramius I hope its okay that I create a dedicated PR and supersede #126 as I am unable to push to your fork.

laminas-ci.schema.json Outdated Show resolved Hide resolved
src/config/app.spec.ts Show resolved Hide resolved
src/config/app.spec.ts Outdated Show resolved Hide resolved
Ocramius and others added 9 commits July 11, 2023 18:17
…E_REF` environment variable

This also introduces a new tool type `ToolRunningContainerDefaultPhpVersion`. This is used in case tools are pre-installed within the CI container as it is the case for `roave-backward-compatibility-check`.

By having an option available for `backwardCompatibilityCheck`, projects can opt-in for these kind of checks. This flag will be enabled by-default with v2 and thus changes to opt-out.

Signed-off-by: Maximilian Bösing <2189546+boesing@users.noreply.github.com>
This also adds a dedicated test for detecting the target reference from environment using `dotenv`

Signed-off-by: Maximilian Bösing <2189546+boesing@users.noreply.github.com>
…mport

Signed-off-by: Maximilian Bösing <2189546+boesing@users.noreply.github.com>
Signed-off-by: Maximilian Bösing <2189546+boesing@users.noreply.github.com>
Signed-off-by: Maximilian Bösing <2189546+boesing@users.noreply.github.com>
Signed-off-by: Maximilian Bösing <2189546+boesing@users.noreply.github.com>
…-ci.schema.json`

Signed-off-by: Maximilian Bösing <2189546+boesing@users.noreply.github.com>
Signed-off-by: Maximilian Bösing <2189546+boesing@users.noreply.github.com>
@boesing boesing merged commit c741f71 into laminas:1.23.x Jul 11, 2023
42 checks passed
@boesing boesing deleted the feature/roave-bc-checker branch July 11, 2023 16:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants