What feature do you want to see added?
I'm a bit unsure about this. While I'd like to track the PRs created by the plugin, I'm not completely certain if it's ethically acceptable to do so. If we decide to proceed, of course, it would be clearly stated in the README.md file, but...
I've developed a script that generates a Google Sheets document listing the PRs created by @jonesbusy and @gounthar. However, since anyone can launch the tool, I can't track campaigns beyond just Valentin's and mine.
Since we don't yet have a way to store the information gathered for the community, we could use the GitHub API to create issues—one per recipe, for example. Each time a recipe is applied to a plugin by anyone and results in a pull request, we could log it as a comment in the dedicated issue. This could also help prevent creating the same recipe for a plugin that already has a stale PR for the same recipe, initiated by another user.
Upstream changes
No response
Are you interested in contributing this feature?
No response
What feature do you want to see added?
I'm a bit unsure about this. While I'd like to track the PRs created by the plugin, I'm not completely certain if it's ethically acceptable to do so. If we decide to proceed, of course, it would be clearly stated in the
README.mdfile, but...I've developed a script that generates a Google Sheets document listing the PRs created by @jonesbusy and @gounthar. However, since anyone can launch the tool, I can't track campaigns beyond just Valentin's and mine.
Since we don't yet have a way to store the information gathered for the community, we could use the GitHub API to create issues—one per recipe, for example. Each time a recipe is applied to a plugin by anyone and results in a pull request, we could log it as a comment in the dedicated issue. This could also help prevent creating the same recipe for a plugin that already has a stale PR for the same recipe, initiated by another user.
Upstream changes
No response
Are you interested in contributing this feature?
No response