Skip to content

chore: the board's built-in "Auto-add to project" workflow has added no item since #2442 #2566

Closed

Description

@JarryShaw

From the 2026-11-01 conventions audit, re-verified on 73add05a3. process.rst, "Milestones and the Project Board": the board's built-in workflows (Auto-add to project, Item closed, Pull request merged, Auto-add sub-issues) do the transitions GitHub can see; project-status.yml only adds a missing item as a fallback.

Decision needed: revive the built-in, or accept project-status.yml as the only adder? Only the owner can open the project's Workflows page (the one place built-ins are configured).

  1. Revive: check Auto-add to project's repository and filter and re-save it; the probe should then show github-project-automation on the next new item.
  2. Accept: amend process.rst to say project-status.yml is the only adder.
    Recommendation: 1, then 2 if the probe still shows only JarryShaw, because 1 is a minute in the web UI and removes the queue delay.
    Fix: per the decision.

Activity

  1. added
    choreMaintenance work: tooling, repo hygiene, no library behaviour change
    needs: decisionWaiting on the maintainer to decide — not blocked by other work
    on Nov 1, 2026
  2. moved this to Needs decision in PyPCAPKiton Nov 1, 2026
  3. JarryShaw commented on Nov 1, 2026

    @JarryShaw
    OwnerAuthor

    I'll do 1. Give me instructions.

  4. JarryShaw commented on Nov 1, 2026

    @JarryShaw
    OwnerAuthor

    Owner chose 1: revive the built-in. Steps:

    1. Open PyPCAPKit, or go to the board's ⋯ menu and choose Workflows.
    2. Select Auto-add to project on the left. The API calls it workflow 7 and says it is enabled.
    3. Click Edit. Set the repository to JarryShaw/PyPCAPKit and the filter to is:issue,pr is:open. Remove any other qualifier, such as a label filter.
    4. Click Save and turn on workflow. Do this even though it already shows as on.
    5. Leave Item added to project off. process.rst explains why: it overwrites the label-derived Status.

    Auto-add only fires for items opened or updated after the save; it does not backfill. On the next new issue or PR, I check its board creator with the probe above. If it is github-project-automation, I close this issue. If it is still JarryShaw, option 2 follows: process.rst will name project-status.yml as the only adder.

  5. added
    wipWork in flight - a covering PR is open or an agent is actively on it
    and removed
    needs: decisionWaiting on the maintainer to decide — not blocked by other work
    on Nov 1, 2026
  6. moved this from Needs decision to WIP in PyPCAPKiton Nov 1, 2026
  7. JarryShaw commented on Nov 1, 2026

    @JarryShaw
    OwnerAuthor

    done

  8. JarryShaw commented on Nov 1, 2026

    @JarryShaw
    OwnerAuthor

    Thanks. You've re-saved Auto-add to project, so the check now waits for the first item opened after the save. Up to #2584, every board item's creator is still JarryShaw. #2585 and #2586 were opened just before the save and aren't on the board yet. I'll run the probe on the next PR I open and post the result here: github-project-automation closes this issue, and JarryShaw moves it to option 2.

  9. JarryShaw commented on Nov 1, 2026

    @JarryShaw
    OwnerAuthor

    The re-save worked. #2587, the first PR opened after it, went onto the board within seconds with creator github-project-automation. #2585, opened just before the save, was added by JarryShaw (project-status.yml). Auto-add to project is adding items again, so project-status.yml is back to being the fallback that process.rst describes. Closing.

  10. removed
    wipWork in flight - a covering PR is open or an agent is actively on it
    on Nov 1, 2026
  11. added this to the PyPCAPKit v1.6 milestone on Nov 2, 2026
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

    choreMaintenance work: tooling, repo hygiene, no library behaviour change

    Projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions