Revise merge instructions for develop to trunk#291
Conversation
Updated instructions for merging develop into trunk to include pulling the latest changes first. Co-authored-by: dkotter <[email protected]>
|
The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message. To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook. |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## develop #291 +/- ##
==========================================
Coverage 57.72% 57.72%
Complexity 567 567
==========================================
Files 36 36
Lines 2933 2933
==========================================
Hits 1693 1693
Misses 1240 1240
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
Updated instructions for merging develop into trunk to include pulling the latest changes first.
What?
This follows-on from @dkotter's suggestion in #280 (comment).
Why?
How?
Use of AI Tools
Testing Instructions
Testing Instructions for Keyboard
Screenshots or screencast