processing/p5.js

Auto-link / Close Issues for 2.0 PRs (p5.js & p5.js-website)

Open

#7,975 opened on Jul 17, 2025

View on GitHub
 (7 comments) (3 reactions) (0 assignees)JavaScript (3,178 forks)batch import
DevOpsFeature RequestHelp Wanted

Repository metrics

Stars
 (20,784 stars)
PR merge metrics
 (Avg merge 9d 8h) (56 merged PRs in 30d)

Description

Increasing access

GitHub’s auto‑link / auto‑close keywords (Resolves #123, Fixes #123, etc.) only work when a PR targets the default branch (main). For PRs into dev-2.0, the keywords are ignored. Example: p5.js PR #7971 included Resolves #7905 but the issue was not linked or closed. Same problem in p5.js-website PRs to 2.0 branch.

Most appropriate sub-area of p5.js?

  • Accessibility
  • Color
  • Core/Environment/Rendering
  • Data
  • DOM
  • Events
  • Image
  • IO
  • Math
  • Typography
  • Utilities
  • WebGL
  • Build process
  • Unit testing
  • Internationalization
  • Friendly errors
  • Other (specify if possible)

Feature request details

Add a GitHub Action (workflow) that runs when a PR into dev-2.0 is merged in p5.js. (similar in p5.js-website with 2.0 branch) It should:

  1. Parse the PR body for Resolves #issue-number.
  2. Link the issue to that PR.
  3. Close issues immediately when merged. (I think this step will be done by github after linking).

This action should be included in both the repo, i.e. p5.js and p5.js-website

Contributor guide

Research direction
Research GitHub Actions workflow triggers (pull request, pull request target), use GitHub API to parse PR body for 'Resolves #issue number', link issues, and close on merge. Examine existing actions like 'auto link' or implement custom action.
Tech stack
javascriptgithub actions
Domain
developer experienceci cdtooling
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitGitHub ActionsJavaScript
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75