[wp-trac] [WordPress Trac] #55422: Add a .git-blame-ignore-revs file

WordPress Trac noreply at wordpress.org
Mon Mar 21 23:50:49 UTC 2022

#55422: Add a .git-blame-ignore-revs file
 Reporter:  helen        |       Owner:  (none)
     Type:  enhancement  |      Status:  new
 Priority:  normal       |   Milestone:  Awaiting Review
Component:  General      |     Version:
 Severity:  minor        |  Resolution:
 Keywords:  has-patch    |     Focuses:

Comment (by costdev):

 @helen I'll be going through the commits you have listed to check them as

 What do you think is the best way to make commit suggestions for
 [https://github.com/WordPress/wordpress-develop/pull/2433 PR 2433]? Should
 we just leave a review comment on `# PHPCS`, for example, with the hashes
 and changesets so that they can be considered for the addition?

 Aside from that, we have `# Pinking shears` and `# PHPCS` at the moment.
 This seems like a manageable limit for now given the number of "Coding
 Standards" commits to be checked.

 I'm curious about everyone's thoughts on the approach and wonder when we
 should consider the PR for merging into Core. If the idea has support,
 should we commit the PR once commits have been reviewed and verified as
 stylistic-only changes, then proceed with additional PRs in a step-by-step
 approach, or?

Ticket URL: <https://core.trac.wordpress.org/ticket/55422#comment:5>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform

More information about the wp-trac mailing list