Skip to content

docs: add about PR commits#6437

Merged
kenjis merged 5 commits intocodeigniter4:developfrom
kenjis:add-docs-on-PR-commits
Aug 28, 2022
Merged

docs: add about PR commits#6437
kenjis merged 5 commits intocodeigniter4:developfrom
kenjis:add-docs-on-PR-commits

Conversation

@kenjis
Copy link
Copy Markdown
Member

@kenjis kenjis commented Aug 28, 2022

Description
Big commits and/or inappropriate commit messages make the reviews difficult.

Checklist:

  • Securely signed commits
  • [] Component(s) with PHPDoc blocks, only if necessary or adds value
  • [] Unit testing, with >80% coverage
  • [] User guide updated
  • [] Conforms to style guide

Copy link
Copy Markdown
Member

@MGatner MGatner left a comment

Choose a reason for hiding this comment

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

Good foundational practices!

9. If there are intermediate commits that are not meaningful to the overall PR, such as "Fixed error on style guide", "Fixed phpstan error", "Fixing mistake in code", and other related commits, it is advised to squash your commits so that we can have a clean commit history.
10. If you have touched PHP code, run static analysis.
- Commit messages are expected to be descriptive of why and what you changed specifically. Commit messages like "Fixes #1234" would be asked by the reviewer to be revised. [Atomic commit](https://en.wikipedia.org/wiki/Atomic_commit#Atomic_commit_convention) is recommended. See [Contribution Workflow](./workflow.md#commit-messages) for details.
9. If you have touched PHP code, run static analysis.
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

We should update composer analyze to dry-run Rector as well, since that is part of our pipeline. I also just realized we aren't using Psalm here! Since you introduced me to it I've added it to all my libraries, and it frequently catches different things from PHPStan (especially around typing). I can look into that.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

I sent #6446

@datamweb
Copy link
Copy Markdown
Contributor

Now that you've created a good guide to writing commits, I thought it would be helpful to add how to edit wrong commits.

https://docs.github.com/en/pull-requests/committing-changes-to-your-project/creating-and-editing-commits/changing-a-commit-message

@kenjis kenjis merged commit a65e57a into codeigniter4:develop Aug 28, 2022
@kenjis kenjis deleted the add-docs-on-PR-commits branch August 28, 2022 22:19
@kenjis
Copy link
Copy Markdown
Member Author

kenjis commented Aug 29, 2022

@datamweb Good reference!
I sent #6447

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.

3 participants