Staging instance, all changes can be removed at any time

Skip to content

browse: provide search routes for GET arg handling

The routes we currently have that /could/ serve for revision/content/origin search cannot be generated on the fly in a Jinja2 template.

These new routes simply adequately redirect standard GET requests with args to our own custom routes.


Migrated from D111 (view on Phabricator)

Merge request reports

Loading