Skip to content

Automated reviewer assignment #319

@ryanking13

Description

@ryanking13

Initially I wanted to experience the process, that's why I am uploading this PR.
Please let me know if you have some concerns about the above automation process (will be implemented w/ power of AI!)

Thanks for the suggestion, but I do not want to get tons of notifications for package update PRs. For now, we have a centralized repository for recipes, but in the future (in the ideal world), each package would have separate repository with separate recipe maintainers. Then, it should be their responsibility to maintain each package.

@ryanking13, the emscripten-forge channel has a GitHub App linked to @emscripten-forge-bot. This bot is capable of merging recipes if all tests pass, linter validation is successful, and tests are present in the first place (or fail otherwise). However, I prefer not to have a completely autonomous bot due to security concerns. So, until we establish a separate repository for each package, a plausible solution would be for the bot to ping the recipe maintainers instead of us. When a contributor submits a pull request (PR) for a recipe and expresses interest in maintaining it, their name will appear in the "Review" tab with the note "recently edited these files" in future PRs intended to update that recipe.

We could have also experimented with CODEOWNERS for this, but this requires individuals to have "maintain" access to the repository.

Originally posted by @agriyakhetarpal in #318 (comment)

Metadata

Metadata

Assignees

No one assigned

    Labels

    OSSCA2025good first issueThese items are marked as good for newcomers to this repository. We truly appreciate the support!help wantedExtra attention is needed. If you're able and willing to take it up, please do!

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions