GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — Automate Python triage membership. · Issue #350 · python/core-workflow

Automate Python triage membership. #350

New issue
Copy link
New issue
Copy link
Closed as not planned
Closed as not planned
Automate Python triage membership.#350
Copy link

Description

@Mariatta
Mariatta
opened on Aug 9, 2019
Issue body actions

It is possible to automate the process for adding people to the Python Triage Team.

  1. A ticket is opened in core-workflow for adding a person to the triage team
  2. Any core dev can approve the request by applying "approved" label
  3. a bot (or script or GitHub App or GitHub Action) automatically invites the person to the team after seeing the "approved" label. It can expand upon the script in https://github.com/python/core-workflow/blob/master/utils/triage_team.py
    3.1 if "approved" label was not added by Python core team member, remove it.
  4. bot automatically closes the issue after triager was invited.

Similar bot: https://github.com/python-trio/snekomatic

For this purpose the bot needs "admin" access to Python org.

For security reason, the access token or secret for the bot should be stored as environment variable, and visible only by select people.

Also for security reason, write access to the bot's code can be restricted to a small group of people only, instead of to all core developers.

Activity

  1. ezio-melotti commented on May 5, 2022

    @ezio-melotti
    ezio-melotti
    on May 5, 2022
    Member
    More actions

    I proposed something similar in python/devguide#848.

  2. AA-Turner commented on Aug 12, 2025

    @AA-Turner
    AA-Turner
    on Aug 12, 2025
    Member
    More actions

    Closing, stale. I think the current process seems to work ok (relevant core dev pings org owners), the volume of new triagers is fairly low & adding a bot that can add users to @python has security implications etc.

    A

  3. AA-Turner
    closed this as not plannedon Aug 12, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions

      You are visitor 01402520 — GeezerVison does not store the pages you look up.
      Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.