-
Notifications
You must be signed in to change notification settings - Fork 9.4k
Working with commits
David Manners edited this page Jun 14, 2019
·
5 revisions
While providing your contribution to the Magento code base it is important to accompany it with a meaningful commit message. Meaningful commit message is important to:
- Help speed up the reviewing process
- Help us write a good release note
- Help future developers understand why a particular change was made
We recommend including the github issue number and title, as well as some additional comments that you feel are relevant.
magento/magento2#<issue-number>: <issue-title>
- <additional comment>
magento/magento2#8618: Apply coupon code button issue on checkout
- fixed issue with assigning coupon_code value from totals
- If it feels hard to summarize what your commit is, then try splitting it into multiple commits,
- If there is no github issue please feel free to miss out the
magento/magento2#<issue-number>:
section and just add a meaningful title, - If you are working on a community project please update the issue part as appropriate, for example, import export should be
magento-engcom/import-export-improvements#<issue-number>:
Interested in becoming a Magento Contributor? Click here to join our Slack workspace! Then come say hi in #general, follow the #announcements, and browse to find more cool channels!
- Getting Started
- Forking and Branching
- Working with commits
- Working Issues and PRs
- Community Maintainers
- Working with commits
- Magento Contributor Assistant
- Magento Automated Testing
- Test coverage contributions
- Slack Channels
- Magento 2 Core
- Multi Source Inventory
- Coding Standard
- DevDocs
- PHP 8 Compatibility
- Platform Health