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
Mike Kistler said: "some automation used to exist in the PR Template picker when teams don’t select a template, the automation would apply the correct template to the PR after it was created, he wants to know if we can add this back.
Mike said A quick search in the azure-rest-api-specs repo suggests that 229 open PRs did not actually choose a PR template https://github.com/Azure/azure-rest-api-specs/pulls?q=is%3Apr+is%3Aopen+%22Choose+a+PR+Template%22"
Wes Haggard added: "a lot of these are coming from the fact folks are submitting a PR via cli or VS code which doesn't really give folks an option to select a template. It is worth filing an issue in the azure-rest-api-specs repo about potentially selecting the template based on what we detect in the PR (i.e. mgmt or data) and then updating the text accordingly"
The text was updated successfully, but these errors were encountered:
API Spec link
.
API Spec version
.
Please describe the feature.
Mike Kistler said: "some automation used to exist in the PR Template picker when teams don’t select a template, the automation would apply the correct template to the PR after it was created, he wants to know if we can add this back.
Mike said A quick search in the azure-rest-api-specs repo suggests that 229 open PRs did not actually choose a PR template https://github.com/Azure/azure-rest-api-specs/pulls?q=is%3Apr+is%3Aopen+%22Choose+a+PR+Template%22"
Wes Haggard added: "a lot of these are coming from the fact folks are submitting a PR via cli or VS code which doesn't really give folks an option to select a template. It is worth filing an issue in the azure-rest-api-specs repo about potentially selecting the template based on what we detect in the PR (i.e. mgmt or data) and then updating the text accordingly"
The text was updated successfully, but these errors were encountered: