Initial boilerplate #1
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
asgrim
commented
Feb 29, 2024
asgrim
force-pushed
the
initial-boilerplate
branch
from
d3e55e4 to
1342044
Compare
asgrim
force-pushed
the
initial-boilerplate
branch
from
1342044 to
c40af18
Compare
Seldaek
reviewed
Feb 29, 2024
asgrim
commented
Mar 8, 2024
theofidry
reviewed
Mar 8, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Some assumptions/opinions made for the development of the tool are:
doctrine/coding-standardfor CS; I feel this CS is comprehensive and fixes most code in a predictable way, and I am most familiar withphpcs(over say, php-cs-fixer).laminas/workflow-continuous-integrationto run the CI workflow, as it is ludicrously easy to get up and running. Should we need to expand out of these realms in the future for static analysis/CS/linting/testing etc., we can of course