feat: add-to-cc-board Github action created.
#2302
Conversation
This is a label trigger to add an Issue o PR to the frontend Core Contributor project board
openedx-webhooks
added
the
open-source-contribution
|
Thanks for the pull request, @ChrisChV! This repository is currently maintained by 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 approvalIf you haven't already, check this list to see if your contribution needs to go through the product review process.
🔘 Provide contextTo 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:
🔘 Get a green buildIf one or more checks are failing, continue working on your changes until this is no longer the case and your build turns green. 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: 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:
💡 As a result it may take up to several weeks or months to complete a review and merge your PR. |
|
@bradenmacdonald could you review this? |
|
@ChrisChV Sure, but could you please explain more about how this works and how to test it? What is the trigger - when a PR is assigned to a CC, or when an issue is assigned to a CC, or when a CC opens a PR? Can you include a link to the "the frontend Core Contributor project board" ? How does the status get updated once it's on the board - manually or automatically? Can it apply retroactively? |
@bradenmacdonald Thanks, I updated the description with more details of this action.
For now, manually, but we are thinking of automating it as well, if the initial MVP works.
Yes, but adding the label manually About testing this, I haven't found a way to test it in the openedx organization, but in the description, I've added a way to test it in a sandbox, if that doesn't work, I could try implementing it in the open-craft organization. |
There was a problem hiding this comment.
OK, approved! Let's merge and try it on here, and if it's working then I'll approve openedx/edx-platform#37044 as well (remind me)
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #2302 +/- ##
=======================================
Coverage 94.64% 94.64%
=======================================
Files 1187 1187
Lines 26220 26220
Branches 5679 5679
=======================================
Hits 24817 24817
Misses 1344 1344
Partials 59 59 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
@bradenmacdonald I tested the action, it raised this issue. I fixed it in #2441 |
|
Status update: We got this issue related to the |
Description
Core Contributor assigneelabel as a trigger.add-to-cc-boardGithub action created. edx-platform#37044PROJECTS_TOKENwith a Github token with these scopes:read:org,project(Created in: [GH Request] Create a new organization secret to be used in projects automatizations axim-engineering#1523)Supporting information
Testing instructions
Testing on the sandbox
openedxorg is already configured and merged: feat: Action to add an issue or PR to a CC board .github#169Core Contributor assigneelabel. Verify that the issue is added to the board edx-platformCore Contributor assigneelabel. Verify that the PR is added to the board edx-platformDeadline
None
Other information
PROJECTS_TOKENwith a Github token with these scopes:read:org,project(Created in: [GH Request] Create a new organization secret to be used in projects automatizations axim-engineering#1523)