Update "New Tag" page to reuse the "New Release" form

Problem to solve

Once #214244 (closed) is completed, we will have two ways of creating Releases through the UI:

  • The old New Tags page
  • The new New Release page

New Tags page

Screenshot_2020-08-12_at_16.25.51

Screenshot_2020-08-12_at_16.25.58

New Release page

Screenshot_2020-08-12_at_16.26.14

Screenshot_2020-08-12_at_16.26.22

Proposal

Update the old New Tags page to reuse the New Release form. The end result will be two pages (New Tag and New Release) that share a common implementation are almost identical, except for a few small differences:

  • The pages will have different URLs (/-/tags/new vs /-/releases/new), titles, and breadcrumbs

  • On the New Tag page, the Release portion of the form will be collapsed by default. This avoids making this page too Release-focused for users who don't use Releases (or users who use tags for purposes other than Releases).

  • Don't forget to clean old workarounds. Just grep for https://gitlab.com/gitlab-org/gitlab/-/issues/214245 in the codebase

Intended users

Background

This proposal was originally discussed in #211692 (closed), but was broken down here into two issues:

Permissions and Security

This page should follow existing documented permissions for both tags and Releases.

Documentation

Yes, this change will require documentation updates. Any documentation page that involves tag creation will likely need to be updated.

Edited by Sean Carroll