Skip to content

Conversation

NalinDalal
Copy link
Contributor

So basically whenever someone creates a pr, then when maintainer comments:

Resolves https://github.com/processing/p5.js/issues/7975

so it handles by itself, tried for like test-merge-action to my own feature-branch
Resolves #7962

Changes:
Introduced a yaml file for same

Screenshots of the change:
workflow run
local pr test

PR Checklist

@perminder-17
Copy link
Collaborator

Hi @NalinDalal,

Thank you for your work on this. I tested it at perminder-17#4, and it works perfectly.

Since I don’t have access to the main processing/p5.js repository settings, I’m not entirely sure whether we need to include the permissions: issues: write and pull-requests: read block.

Screenshot from 2025-07-28 20-41-59

Does the upstream processing/p5.js repository use the same configuration? The image above shows my fork’s settings. @ksen0 @limzykenneth ?

@NalinDalal
Copy link
Contributor Author

I am also concerned about same, anyways thanks @perminder-17 😁

@NalinDalal NalinDalal closed this Aug 8, 2025
@NalinDalal NalinDalal deleted the my-feature-branch branch August 8, 2025 06:29
@NalinDalal NalinDalal restored the my-feature-branch branch August 8, 2025 07:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants