Skip to content

[Test] Re-trigger CI to test rector-laravel with update to use rector/rector:dev-main - #8364

Closed
samsonasik wants to merge 1 commit into
mainfrom
test-rector-laravle
Closed

[Test] Re-trigger CI to test rector-laravel with update to use rector/rector:dev-main#8364
samsonasik wants to merge 1 commit into
mainfrom
test-rector-laravle

Conversation

@samsonasik

Copy link
Copy Markdown
Member

@samsonasik
samsonasik marked this pull request as draft August 24, 2026 09:50
@samsonasik
samsonasik marked this pull request as ready for review August 24, 2026 09:51
@samsonasiksamsonasik changed the title [Test] Test rector-laravel with update to use rector/rector:dev-main[Test] Re-trigger CI to test rector-laravel with update to use rector/rector:dev-mainAug 24, 2026
@samsonasik

Copy link
Copy Markdown
MemberAuthor

@TomasVotruba here PR to retrigger CI on latest build of rector/rector dev-main and show error in both rector-drupal and rector-laravel:

@TomasVotruba

Copy link
Copy Markdown
Member

This should happen before merge and test the PR, can you update tests to make it so?

@samsonasik

Copy link
Copy Markdown
MemberAuthor

seems not possible, because rector-src is not installable on that packages as the they consume scoped rector/rector

@TomasVotruba

Copy link
Copy Markdown
Member

I see, we'll have to find a way.

@samsonasik

Copy link
Copy Markdown
MemberAuthor

Rebased for re-trigger CI

@TomasVotruba

Copy link
Copy Markdown
Member

Already part of standard CI runs

@TomasVotruba
TomasVotruba deleted the test-rector-laravle branch August 24, 2026 23:23
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

@samsonasik@TomasVotruba