-
-
Notifications
You must be signed in to change notification settings - Fork 30
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
Use brick's organization coding standards #62
base: master
Are you sure you want to change the base?
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,10 @@ | ||
name: Coding Standards | ||
|
||
on: | ||
pull_request: | ||
push: | ||
|
||
jobs: | ||
coding-standards: | ||
name: Coding Standards | ||
uses: brick/coding-standards/.github/workflows/coding-standards.yml@main | ||
This file was deleted.
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,8 +1,6 @@ | ||
{ | ||
"require": { | ||
"symplify/easy-coding-standard": "^10.3", | ||
"slevomat/coding-standard": "^7.2", | ||
"squizlabs/php_codesniffer": "^3.7" | ||
"brick/coding-standards": "dev-main" | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Should this still be in There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Yes it should stay isolated because However you raise a good point about psalm. This meta package cannot group multiple tools into one package as it would fall into the dependency problem we tried to avoid in the first place. The best option IMO would be to let each brick libraries require the tools independently and only use the coding-standards repo to share tools configuration files and github workflows. This would bring some flexibility. Downside is, every time there's a new tool version, each brick libraries have to be updated one by one. Could be automated at some point though. AFAIU this what doctrine is doing. |
||
}, | ||
"config": { | ||
"allow-plugins": { | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Will this workflow run both ECS & Psalm from the coding standards repo, or do you want to separate them into different workflows? In the latter case, I'd prefer to keep the name
coding-style
if we're going to run ECS only.I basically consider the coding standards repo as containing:
coding-style
: ECSstatic-analysis
: PsalmWDYT?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah agreed, let's add psalm workflow to this repository and properly split things like you mentioned.