Community contribution label

[iamshobhraj]

Description

Add GitHub Actions workflow to automatically manage the "community-contribution-in-progress" label on issues based on external contributor assignments. This PR adds both the workflow configuration and the label management script.

Issue addressed

Addresses learningequality/kolibri#12923

Changelog

• Description: Add automated workflow system for managing community contribution labels on issues, including a reusable GitHub Action workflow and supporting Python script
• Products impact: none
• Addresses: Create a new GitHub action that adds/removes "community-contribution-in-progress" label on issues kolibri#12923
• Components: GitHub Actions, automation
• Breaking: no
• Impacts a11y: no
• Guidance: To use this workflow, reference it from your repository's workflow files using workflow_call

Steps to test

1. Set up a repository to call this reusable workflow
2. Assign an issue to an external contributor
   • Verify the label is automatically added
3. Unassign the issue
   • Verify the label is automatically removed
4. Test with internal contributors
   • Verify the label behavior is correct

(optional) Implementation notes

At a high level, how did you implement this?

This PR adds:

1. A reusable GitHub Actions workflow (community-contribution-label.yml)
2. A Python script to handle the label management logic (community-contribution-label.py)

The workflow:

• Is triggered as a reusable workflow
• Uses Python to interact with GitHub API
• Manages labels based on assignee status (internal/external)

The script:

• Checks if issue assignees are external contributors
• Adds/removes the 'community-contribution-in-progress' label accordingly
• Handles GitHub API interactions securely

Testing checklist

• Contributor has fully tested the PR manually
• If there are any front-end changes, before/after screenshots are included (N/A)
• Critical and brittle code paths are covered by unit tests
• The change is described in the changelog section above

Reviewer guidance

• Is the code clean and well-commented?
• Are there tests for this change?
• Are all UI components LTR and RTL compliant (if applicable)?
• Add other things to check for here

After review

• The changelog item has been pasted to the CHANGELOG.md

Comments

[MisRob]

Thank you, @iamshobhraj, we will review.

Following-up on your comment

Since I had to use this GitHub Action in my personal repository, I created and used GitHub tokens. For the organization, we'll need to ensure we have a similar token set up if it isn’t already covered.

I think this @rtibbles's guidance from another pull request should be relevant

For the Github token, we will be using the LE Github App for authentication. You can see how we use the token generation action by tibdex here: https://github.com/learningequality/kolibri/blob/develop/.github/workflows/update_h5p.yml#L84 to use those secrets to generate a token we can use for Github authentication.

[iamshobhraj]

@MisRob i added the tidbex token generation, but i dont know if the token generated will have the permissions needed to add label to issues and read collaborators from the repository.

[MisRob]

Thanks @iamshobhraj, we will test that and follow-up