CI: use a snapshot of core's phpcs rules as changes in Drupal core will break MRs with limited benefit to module development

I specifically opted to chase it because otherwise we get the feedback/complaint that we’re trailing HEAD too far.

But I agree that 2 breaks in 1 week is too much.

(Too bad that core doesn’t batch these — that’d have made it much more bearable.)

I specifically opted to chase it because otherwise we get the feedback/complaint that we’re trailing HEAD too far.

Are we going to be in core anytime soon? I am unsure why it matters if we are month or 2 behind. does this really change that much?

Since I doubt anything will get into core before the demo in Barcelona it seems that we should favor development speed over keeping up with core's phpcs rules.

then? That'd match Drupal 10.x's rules, which won't change as much.

That seems better but 📌 Fix 'Drupal.Commenting.InlineComment.NotCapital' coding standard Fixed was still committed to 10.x branches.

I am going to change the MR to a draft try a couple of ideas. Basically allow us to get a warning if we haven't updated in phpcs rules in X number of days

Think this is ready for review. I used the core/php.xml.dist file before 📌 Fix 'Drupal.Commenting.InlineComment.NotCapital' coding standard Fixed was committed.

You can see the shows a new warning that our core.phpcs.xml.dist file is out of date but phpcs job passes. https://git.drupalcode.org/project/experience_builder/-/pipelines/231385

I also ran pipeline with were I copied the most recent core/php.xml.dist. This passed the new job to check to see if the phpcs was up to date but failed the phcs job because we are not up to date with all the rules. https://git.drupalcode.org/project/experience_builder/-/pipelines/231381

Wim Leers → credited bnjmnm → .

the new phpcs-rules-match-drupal-11 job

👏 Great call! 😄

Automatically closed - issue fixed for 2 weeks with no activity.