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

Add community-cc-list.md file #228

Merged
merged 1 commit into from
Jan 19, 2024
Merged

Conversation

jrfnl
Copy link
Member

@jrfnl jrfnl commented Jan 4, 2024

Description

This adds the initial wider PHP_CodeSniffer community cc list file as proposed in #227.

Suggested changelog entry

N/A

Related issues/external references

Closes #227

@michalbundyra
Copy link
Contributor

@jrfnl please add me in as well, thanks ❤️

For more context, see https://github.com/PHPCSStandards/PHP_CodeSniffer/issues/227
-->

/cc @kukulich, @greg0ire @Ocramius
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Putting each user on a separate line will make code reviews easier in future.

Is there intentionally a difference between a comma and a space for separating usernames?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The comma/space was a typo from my side which I've corrected.

As for putting each handle on a separate line - good point.

I'm a bit in doubt though on whether to do that as yes, it will make a PR diff easier to review, but on the other hand, it will make using the list more cumbersome as I'd normally want to copy/paste this as a one-liner in the ticket text and having each user on a separate line would require editing the paste to remove the new lines.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think just using space with the list would look a bit more like the codeowners file, so I'd probably opt to follow that convention as well.

@jrfnl jrfnl force-pushed the feature/227-community-cc-list branch from e904e45 to 033dad0 Compare January 5, 2024 09:23
@jrfnl
Copy link
Member Author

jrfnl commented Jan 5, 2024

@michalbundyra Added!

@jrfnl jrfnl force-pushed the feature/227-community-cc-list branch from 033dad0 to 4d4f2a4 Compare January 5, 2024 09:33
@jrfnl jrfnl force-pushed the feature/227-community-cc-list branch from 4d4f2a4 to 680f7c3 Compare January 5, 2024 17:28
@jrfnl jrfnl force-pushed the feature/227-community-cc-list branch from 680f7c3 to 65afb16 Compare January 19, 2024 03:33
This adds the initial cc list file.

Fixes 227
@jrfnl jrfnl force-pushed the feature/227-community-cc-list branch from 65afb16 to 73e959c Compare January 19, 2024 03:36
@jrfnl jrfnl added this to the 3.8.x Next milestone Jan 19, 2024
@jrfnl jrfnl merged commit 8700587 into master Jan 19, 2024
38 checks passed
@jrfnl jrfnl deleted the feature/227-community-cc-list branch January 19, 2024 03:41
@jrfnl jrfnl modified the milestones: 3.8.x Next, 3.9.0 Jan 19, 2024
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.

Proposal: Informing external standards/integrators of important changes/tickets asking for community input
5 participants