57 review and streamline contributor and developer documentation#169
Conversation
…md`, `EXPERIMENTS_DEVELOPER_GUIDE.md`, and `RELEASE_INSTRUCTIONS.md`. Updated `CONTRIBUTING.md` to include revised setup and coding standards.
…EW.md` and add REST API testing documentation
|
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 Unlinked AccountsThe following contributors have not linked their GitHub and WordPress.org accounts: @pbearne@git.wordpress.org, @hrishikesh2810. Contributors, please read how to link your accounts to ensure your work is properly credited in WordPress releases. 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 #169 +/- ##
==========================================
Coverage 50.30% 50.30%
Complexity 381 381
==========================================
Files 27 27
Lines 1998 1998
==========================================
Hits 1005 1005
Misses 993 993
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:
|
|
@pbearne would be great to get your GitHub and WPORG accounts linked (see bot message above) as that makes crediting back to WPORG accounts more automated/reliable. |
CONTRIBUTING.md
Outdated
| * `develop`: The main development branch. | ||
| * `trunk`: The stable release branch. | ||
| * `release/*`: A branch for a specific release, useful e.g. for applying a hotfix. | ||
| * `feature/*`: A branch for a larger feature that takes multiple iterative PRs towards completion. |
There was a problem hiding this comment.
We haven't been following this so I'd suggest we remove it
There was a problem hiding this comment.
What should we have instead?
Co-authored-by: Darin Kotter <darin.kotter@gmail.com>
Co-authored-by: Darin Kotter <darin.kotter@gmail.com>
Co-authored-by: Darin Kotter <darin.kotter@gmail.com>
Co-authored-by: Darin Kotter <darin.kotter@gmail.com>
Co-authored-by: Darin Kotter <darin.kotter@gmail.com>
|
@pbearne I've applied most of the recommended changes here, would you mind handling the rest called out above? |
…developer-documentation # Conflicts: # CONTRIBUTING.md # docs/DEVELOPER_GUIDE.md
…, refine `CONTRIBUTING.md` setup and branch guidelines.
Co-authored-by: Darin Kotter <darin.kotter@gmail.com>
Removed detailed release instructions and added a link to a separate document for release steps.
…developer-documentation
What?
Closes #57
Why?