You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We've had a couple of "first time" contributors open PRs recently but get tripped up by the auto PR template.
Given that the vast majority of our PRs seem to fall into the Misc: Bug Fix, New Feature, Documentation Update, Other category, I'm wondering if we ought to consider doing something like:
dropping the PR body rewrite action and just having a generic PR template
creating issue templates for the tools, components, requirements, and samplings that capture the current requirements for each of those types
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
We've had a couple of "first time" contributors open PRs recently but get tripped up by the auto PR template.
Given that the vast majority of our PRs seem to fall into the
Misc: Bug Fix, New Feature, Documentation Update, Othercategory, I'm wondering if we ought to consider doing something like:Beta Was this translation helpful? Give feedback.
All reactions