gitea/templates/repo/issue/search.tmpl

<form class="ui form ignore-dirty">
	<div class="ui search fluid action input">
		<input type="hidden" name="type" value="{{$.ViewType}}"/>
		<input type="hidden" name="state" value="{{$.State}}"/>
		<input type="hidden" name="labels" value="{{.SelectLabels}}"/>
		<input type="hidden" name="milestone" value="{{$.MilestoneID}}"/>
		<input type="hidden" name="assignee" value="{{$.AssigneeID}}"/>
		<input type="hidden" name="poster" value="{{$.PosterID}}"/>
		<input name="q" value="{{.Keyword}}" placeholder="{{.locale.Tr "explore.search"}}...">
		<button class="ui primary button" type="submit">{{.locale.Tr "explore.search"}}</button>
	</div>
</form>
Don't warn users about every dirty form (#3707) The choice regarding which forms should or should not trigger a warning is subjective. I tried to be consistent and not warn about forms that: - run an action, rather than edit data: search, send an email. - delete data: a warning about losing data would be confusing Note that forms on sign-in pages were already ignored (using a selector, rather than an explicit class on the form element). Fixes #3698. 2018-03-23 14:10:42 +00:00			`<form class="ui form ignore-dirty">`
Fix search form button overlap (#11840) Co-authored-by: techknowlogick <techknowlogick@gitea.io> 2020-06-12 03:35:03 +00:00			`<div class="ui search fluid action input">`
Search bar for issues/pulls (#530) 2017-01-25 02:43:02 +00:00			`<input type="hidden" name="type" value="{{$.ViewType}}"/>`
			`<input type="hidden" name="state" value="{{$.State}}"/>`
			`<input type="hidden" name="labels" value="{{.SelectLabels}}"/>`
			`<input type="hidden" name="milestone" value="{{$.MilestoneID}}"/>`
			`<input type="hidden" name="assignee" value="{{$.AssigneeID}}"/>`
Add issue filter for Author (#20578) This adds a new filter option on the issues and pulls pages to filter by the author/poster/creator of the issue or PR 2022-08-08 20:03:58 +00:00			`<input type="hidden" name="poster" value="{{$.PosterID}}"/>`
Refactor `i18n` to `locale` (#20153) * Refactor `i18n` to `locale` - Currently we're using the `i18n` variable naming for the `locale` struct. This contains locale's specific information and cannot be used for general i18n purpose, therefore refactoring it to `locale` makes more sense. - Ref: https://github.com/go-gitea/gitea/pull/20096#discussion_r906699200 * Update routers/install/install.go 2022-06-27 20:58:46 +00:00			`<input name="q" value="{{.Keyword}}" placeholder="{{.locale.Tr "explore.search"}}...">`
			`<button class="ui primary button" type="submit">{{.locale.Tr "explore.search"}}</button>`
Search bar for issues/pulls (#530) 2017-01-25 02:43:02 +00:00			`</div>`
			`</form>`