Conversation
|
I mean, ideally people will open PRs instead of issues, no? |
@ohemorange I thought about just a PR template with the structure someone would need as an example snippet. What do you think? |
|
I guess that could work? What problem is that solving? I feel like the json structure makes the basic format clear, and the README, which literally shows up on the main page of the repo, explains what the fields are. Like I guess we could put "have you considered reading the README and opening a PR based on that" but I don't think we encourage a process where we have to manually create a PR from inputs. |
It's not necessarily a rampant problem. Just sometimes I see missing fields in PRs pop up. And figured a template would smooth this over and make it even more clear. |
|
Hm, maybe a PR template with a checklist based on the info from the readme then? |
That works, I can just do that |
Figured it might be useful for future requests. Let me know if it's not really helpful.