-
Notifications
You must be signed in to change notification settings - Fork 128
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Issues templates don't offer a general template #734
Comments
This is on purpose because people would constantly mis-categorize things. There are different contributors focused on different SDKs in this repo - hence different labels are auto applied and different default assignees are used. Specific templates are needed. @cicoyle please be specific as to what kind of issue you would like to file and perhaps I can do some word smithing to be more clear as to which template should be used. I think what you are looking for is: |
Keep in mind that we have 5 SDKs published via this repo:
The latter is the most different and has in essence different maintainers (because most of the work is actually in That is why issue templates are separated into: |
This issue has been automatically marked as stale because it has not had activity in the last 60 days. It will be closed in the next 7 days unless it is tagged (pinned, good first issue, help wanted or triaged/resolved) or other activity occurs. Thank you for your contributions. |
This issue has been automatically closed because it has not had activity in the last 67 days. If this issue is still valid, please ping a maintainer and ask them to label it as pinned, good first issue, help wanted or triaged/resolved. Thank you for your contributions. |
Expected Behavior
I would expect to open a general issue/feature request unrelated to workflows for this sdk. Upon looking at the templates for this sdk I see:
There is no general issue template available to developers to use. I think the template descriptions should be generalized to be more broad, beyond
workflows vs not workflows
Steps to Reproduce the Problem
Open an issue in this sdk.
The text was updated successfully, but these errors were encountered: