-
Notifications
You must be signed in to change notification settings - Fork 70
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
[BUG] Github Request template creates issues in other repos when selected #268
Comments
Hi @dbwiddis Looking at few other repos here, I do not see this issue template being reflected. |
I think sdk repo did not have its own templates thus the issue: |
Admin team is now part of sdk repo. |
Seems like |
Our project board is already sorting on all the repos at the moment, not just .github. |
I made issues show their repositories on the board, and an oncall can manually correct it upon creation. |
Yes, if a template has its own A lot of the older repos have templates from before they were standardized. See:
Ah, yes, that makes sense. Looking around looks like changing the url in the config.yml link could apply, but this just has the links that go below the "Create Issue" buttons. So I don't really know how to have a "local" template in the |
What is the bug?
Other repositories in the
opensearch-project
org are inheriting all of the templates in the.github/ISSUE_TEMPLATES
directory (unless they have their own such directory). For most templates (bug report, feature request, etc.) this is desired behavior. However, the newGITHUB_REQUEST_TEMPLATE
introduced in #238 seems like it should only be visible in this repo and not org-wide.How can one reproduce the bug?
ISSUE_TEMPLATES
directory, and select theIssues
tab.What is the expected behavior?
Either the template is not visible in other repos, or if it must be, the issue is created in the
.github
repo.Do you have any screenshots?
Do you have any additional context?
From the GitHub documentation it appears you can add a
projects:
line to the issue template YAML to identify the repo where the issue should be created.The text was updated successfully, but these errors were encountered: