fix: Add group_id and user_partition_id support to Cohorts API v1

[brianjbuck-wgu]

Description

The Cohorts API v1 POST and PATCH endpoints now support group_id and user_partition_id parameters, enabling content group associations to be set when creating or updating cohorts.

Supporting information

Fixes: #37981

[openedx-webhooks]

Thanks for the pull request, @brianjbuck-wgu!

This repository is currently maintained by @openedx/wg-maintenance-openedx-platform.

Once you've gone through the following steps feel free to tag them in a comment and let them know that your changes are ready for engineering review.

🔘 Get product approval

If you haven't already, check this list to see if your contribution needs to go through the product review process.

• If it does, you'll need to submit a product proposal for your contribution, and have it reviewed by the Product Working Group.
  • This process (including the steps you'll need to take) is documented here.
• If it doesn't, simply proceed with the next step.

🔘 Provide context

To help your reviewers and other members of the community understand the purpose and larger context of your changes, feel free to add as much of the following information to the PR description as you can:

• Dependencies

  This PR must be merged before / after / at the same time as ...

• Blockers

  This PR is waiting for OEP-1234 to be accepted.

• Timeline information

  This PR must be merged by XX date because ...

• Partner information

  This is for a course on edx.org.

• Supporting documentation
• Relevant Open edX discussion forum threads

🔘 Get a green build

If one or more checks are failing, continue working on your changes until this is no longer the case and your build turns green.

Details

---

Where can I find more information?

If you'd like to get more details on all aspects of the review process for open source pull requests (OSPRs), check out the following resources:

• Overview of Review Process for Community Contributions
• Pull Request Status Guide
• Making changes to your pull request

When can I expect my changes to be merged?

Our goal is to get community contributions seen and reviewed as efficiently as possible.

However, the amount of time that it takes to review and merge a PR can vary significantly based on factors such as:

• The size and impact of the changes that it introduces
• The need for product review
• Maintenance status of the parent repository

💡 As a result it may take up to several weeks or months to complete a review and merge your PR.

[Copilot]

Pull request overview

This PR adds support for group_id and user_partition_id parameters to the Cohorts API v1 POST and PATCH endpoints, enabling content group associations to be set when creating or updating cohorts.

Changes:

• Added a new helper function _update_cohort_partition_group to handle partition group associations
• Extended POST endpoint to accept optional group_id and user_partition_id parameters for cohort creation
• Extended PATCH endpoint to support updating or removing content group associations via group_id and user_partition_id
• Updated OpenAPI documentation with proper schema definitions for the new parameters

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 1 comment.

File	Description
openedx/core/djangoapps/course_groups/views.py	Added helper function and extended POST/PATCH endpoints to support content group associations
openedx/core/djangoapps/course_groups/tests/test_api_views.py	Added comprehensive test coverage for new functionality including creation, updates, and error cases
docs/lms-openapi.yaml	Updated API documentation with proper schema definitions and descriptions for cohort operations

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.