processing/p5.js
Vedi su GitHubAuto-link / Close Issues for 2.0 PRs (p5.js & p5.js-website)
Open
#7975 aperta il 17 lug 2025
DevOpsFeature RequestHelp Wanted
Metriche repository
- Star
- (20.784 star)
- Metriche merge PR
- (Merge medio 9g 8h) (56 PR mergiate in 30 g)
Descrizione
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:
- Parse the PR body for
Resolves #issue-number. - Link the issue to that PR.
- 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