-
-
Notifications
You must be signed in to change notification settings - Fork 5.8k
Support setting the default
attribute of the issue template dropdown field
#31045
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
Conversation
Please add tests. |
From the code, I am confused what happens when |
…n field (go-gitea#31045) Fix go-gitea#31044 According to [GitHub issue template documentation](https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-githubs-form-schema#attributes-for-dropdown), the `default` attribute can be used to specify the preselected option for a dropdown field.
Yes. If there are no preselected options, the value of the dropdown field defaults to empty, meaning no option is selected. |
Sorry, I haven't refresh the page and just merged. :( |
…n field (#31045) (#31059) Backport #31045 by @Zettat123 Fix #31044 According to [GitHub issue template documentation](https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-githubs-form-schema#attributes-for-dropdown), the `default` attribute can be used to specify the preselected option for a dropdown field. Co-authored-by: Zettat123 <zettat123@gmail.com>
* giteaofficial/main: [skip ci] Updated translations via Crowdin Support setting the `default` attribute of the issue template dropdown field (go-gitea#31045) Alpine 3.20 has been released (go-gitea#31047)
Fix #31044
According to GitHub issue template documentation, the
default
attribute can be used to specify the preselected option for a dropdown field.