Skip to content

Enforce some sort of review process in GitHub #291

Open

Description

@ThomasRules2000

Ideally I shouldn't've just been able to merge a PR without anyone else being involved. We should enforce that at least 1 other maintainer has reviewed the change before allowing merge

Activity

  1. ThomasRules2000 commented on Sep 28, 2025

    @ThomasRules2000
    ContributorAuthor
  2. added
    new featureA mostly separate new command/feature
    and removed
    new featureA mostly separate new command/feature
    on Sep 28, 2025
  3. alimmeek commented on Jan 6, 2026

    @alimmeek
    Contributor
    Image

    thoughts anyone? this seems to be the only way i can do it (not enforced yet)

  4. self-assigned this
    on Mar 8, 2026
  5. raven0034 commented on Mar 8, 2026

    @raven0034
    Member

    Enabled suggestion from alia's comment on this repo, will keep open for now as this is something to look at more broadly alongside how the teams & their respective perms are organised and other bits.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions