feat: add-to-cc-board Github action created.

[ChrisChV]

Description

• This is a label trigger to add an Issue or PR to the edx-platform Core Contributor project board.
• This action uses the Core Contributor assignee label as a trigger.
• This action reuses feat: Action to add an issue or PR to a CC board .github#169 (comment)
• When you add the label to an issue or PR, it is automatically added to the board https://github.com/orgs/openedx/projects/79
• See this document for more technical info
• Which edX user roles will this change impact? "Developer".
• It is necessary to create an organization secret called PROJECTS_TOKEN with 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

• Github issue: Implement and configure test boards in the organization wg-governance#157
• Epic: Use Kanban board for the working workflow wg-governance#138
• Internal ticket: SE-6387

Testing instructions

• There is no way to test this in the organization without being merged, but you can test this same code in a sandbox:
  • repo-edx
  • .github sandbox
  • Sandbox board

Testing on the sandbox

• The reusable action in the sandbox is configured in .github sandbox. The same for the openedx org is already configured and merged: feat: Action to add an issue or PR to a CC board .github#169
• The action for the trigger in the sandbox is configured in repo-edx
• The board in the sandbox is edx-platform
• Create an issue in repo-edx.
• Add the Core Contributor assignee label. Verify that the issue is added to the board edx-platform
• Create a PR in repo-edx.
• Add the Core Contributor assignee label. Verify that the PR is added to the board edx-platform

Deadline

None

Other information

• It is necessary to create an organization secret called PROJECTS_TOKEN with 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)

[openedx-webhooks]

Thanks for the pull request, @ChrisChV!

This repository is currently maintained by @openedx/wg-maintenance-edx-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.

---

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.

[ChrisChV]

@bradenmacdonald could you review this? Also, I don't know if you have permission to create this:

It is necessary to create an organization secret called PROJECTS_TOKEN with a Github token with these scopes: read:org, project

[bradenmacdonald]

@ChrisChV For GitHub tokens and changes like that, you can open a request here: https://github.com/openedx/axim-engineering/issues/new/choose

For this review, I could but I'm not sure I'm the best person as I don't really understand the details of how this is supposed to work. Could you maybe add more testing instructions? How does the "Core Contributor assignee" label get added in the first place? How does the status on the board stay up to date once the issue is created?

[ChrisChV]

For GitHub tokens and changes like that, you can open a request here: https://github.com/openedx/axim-engineering/issues/new/choose

@bradenmacdonald Thanks! It was created in openedx/axim-engineering#1523

Could you maybe add more testing instructions?

Yes, I updated the description with more details of this action, also you can check this document for more details.

How does the "Core Contributor assignee" label get added in the first place? How does the status on the board stay up to date once the issue is created?

The boards are designed so that CCs have a dashboard to view their work as CCs. It's each individual's responsibility to navigate between the statuses on this board. Depending on how the board works, some parts can be automated.

Let me know if you have more questions 😃