E517 ci: Add an AutoReview workflow by theofidry · Pull Request #1375 · phpbrew/phpbrew · GitHub
[go: up one dir, main page]

Skip to content

Conversation

@theofidry
Copy link
Contributor

Introduces a workflow for the purpose of validating and reviewing the code. This where I would typically include:

  • Static analysis
  • Various validations, e.g. that the composer.json is valid (the only check currently implemented in this PR)
  • Code linting
  • Any unit tests that aim at checking the codebase architecture/structure/conventions, i.e. anything that is not testing the source code behaviour.

Introduces a workflow for the purpose of validating and reviewing the
code. This where I would typically include:

- Static analysis
- Various validations, e.g. that the `composer.json` is valid
  (the only check currently implemented in this PR)
- Code linting
- Any unit tests that aim at checking the codebase
  architecture/structure/conventions, i.e. anything that is not testing
the source code behaviour.

on:
push:
branches: [ main, master ]
Copy link
Member

Choose a reason for hiding this comment

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

Could you explain why the main branch is added in the branches setting?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Currently, there is no reason.

I would like however to rename master to main at some point, allowing the two will allow to do that any time without any issue. Note that the other added workflow have the same too

@peter279k
Copy link
Member
peter279k commented Jun 24, 2024

Thanks for your PR. I think the composer.lock should not be changed in the PR. Could you check that?

1000

@theofidry
Copy link
Contributor Author

@peter279k clarified and extracted the composer update in #1379

@peter279k
Copy link
Member

Due to the PR about updating the composer.lock file is extracted from this, I suggest the composer.lock should be reverted in this PR.

@theofidry
Copy link
Contributor Author

done

@theofidry theofidry mentioned this pull request Jun 24, 2024
2 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

Comments

0