You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit fe74e1f
Browse filesBrowse the repository at this point in the historyBrowse files
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -50,8 +50,6 @@ composer format && npm run lint:js:fix && npm run format
50
50
npm run wp-env:test start -- --xdebug=coverage && npm run test:e2e && npm run test:php && npm run wp-env:test stop
51
51
```
52
52
53
-
---
54
-
55
53
### Coding standards
56
54
57
55
All code must follow the [WordPress Coding Standards](https://developer.wordpress.org/coding-standards/). This ensures consistency across the WordPress ecosystem and makes the codebase maintainable.
@@ -144,14 +142,16 @@ echo 'Hello World';
144
142
- As with all WordPress projects, we want to ensure a welcoming environment for everyone. With that in mind, all contributors are expected to follow our [Code of Conduct](https://make.wordpress.org/handbook/community-code-of-conduct/).
145
143
- All WordPress projects are licensed under the GPLv2+, and all contributions to the AI plugin will be released under the GPLv2+ license. You maintain copyright over any contribution you make, and by submitting a pull request, you are agreeing to release that contribution under the GPLv2+ license.
146
144
145
+
---
146
+
147
147
## Additional resources
148
148
149
149
For more detailed information on plugin architecture, creating experiments, and development workflows, see:
150
150
151
151
-[Developer Guide](docs/DEVELOPER_GUIDE.md) - Comprehensive guide to plugin development
152
152
-[Architecture Overview](docs/ARCHITECTURE_OVERVIEW.md) - Comprehensive guide to plugin architecture
153
-
-[Release Instructions](docs/RELEASE_INSTRUCTIONS.md) - Checklist steps for releasing versions of the plugin
153
+
-[Experiment Lifecycle](docs/EXPERIMENT_LIFECYCLE.md) - Defines how new Experiments land in the plugin and how they could graduate towards WordPress core
154
154
-[Testing Strategy](docs/TESTING.md) - Testing philosophy and guidelines
155
155
-[Testing API Strategy](docs/TESTING_REST_API.md) - Testing philosophy and guidelines
156
-
-[Experiment Lifecycle](docs/EXPERIMENT_LIFECYCLE.md) - Defines how new Experiments land in the plugin and how they could graduate towards WordPress core
157
-
-[WordPress AI Team](https://make.wordpress.org/ai/) - Community and discussion
@@ -340,33 +336,25 @@ Push your branch and create a pull request. Follow the contribution guidelines i
340
336
- Pull request requirements
341
337
- Code review process
342
338
339
+
## Merge Strategy
340
+
341
+
This project makes use of squash merges from PR branches to the `develop` branch and as such we've disabled the "Allow merge commits" and "Allow rebase merging" in the repo so that anyone merging will be forced into the "Allow squash merging" approach.
342
+
343
+
Note that not every commit message should be kept in the resulting squash merge commit message, feel free to strip out unhelpful commit messages to keep the resulting squash merge commit message as concise as possible (e.g. get ride of those "lets try this again" commit messages).
344
+
345
+
An example of a squash merge from #359 can be seen in 4c9699f, while an example of the prior approach of a merge commit from #311 can be seen in e63d8c0.
346
+
343
347
---
344
348
345
349
## Additional Resources
346
350
347
-
### Documentation
351
+
For more detailed information on plugin architecture, creating experiments, and development workflows, see:
348
352
349
353
-[Contributing Guidelines](../CONTRIBUTING.md) - Code standards and contribution process
354
+
-[Architecture Overview](docs/ARCHITECTURE_OVERVIEW.md) - Comprehensive guide to plugin architecture
355
+
-[Experiment Lifecycle](EXPERIMENT_LIFECYCLE.md) - Defines how new Experiments land in the plugin and how they could graduate towards WordPress core
350
356
-[Testing Strategy](TESTING.md) – Testing philosophy and guidelines
351
357
-[Testing REST API Strategy](TESTING_REST_API.md) – Guidelines specific to testing REST API integrations
-[Experiment Lifecycle](EXPERIMENT_LIFECYCLE.md) - Defines how new Experiments land in the plugin and how they could graduate towards WordPress core
356
-
-[WordPress AI Team](https://make.wordpress.org/ai/)
357
-
358
-
### Getting Help
359
-
360
-
-**GitHub Issues**: Report bugs or request features
361
-
-**WordPress Slack**: Join the `#core-ai` channel in Slack, see the [WordPress Slack page](https://make.wordpress.org/chat/) for signup information; it is free to join.
Copy file name to clipboardExpand all lines: docs/RELEASE_INSTRUCTIONS.md
-1Lines changed: 0 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,4 +1,3 @@
1
-
2
1
# Release Instructions
3
2
4
3
The following can be copied into a [new, blank GitHub issue](https://github.com/WordPress/ai/issues) who's title is formatted as `Release version X.Y.Z`. Once the issue is submitted, the checklist in the body of the issue should be followed to release a new version of the AI plugin. All references to `X.Y.Z` below should be updated to the actual release version number.
0 commit comments