Skip to content

Add overview of branches and filtered views for active/stale branches

Takuya Noguchi requested to merge tnir/gitlab-foss:40187-project-branch-dashboard-with-active-stale-branches into master

What does this MR do?

Adds overview of project branches and filtered views for active and stale branches.

Are there points in the code the reviewer needs to double check?

Edge: (UPDATED) I integrated the state parameter into URLs and this MR will deprecate old URLs:

Newly introduced URLs

  • /[namespace]/[project]/branches/all: same as previous /[namespace]/[project]/branches
  • /[namespace]/[project]/branches/active: shows only branches updated within 3 months
  • /[namespace]/[project]/branches/stale: shows only branches not updated within 3 months

Redirects with deprecation

  • /[namespace]/[project]/branches?sort=name_asc is redirected to /[namespace]/[project]/branches/all
  • /[namespace]/[project]/branches?search=master is redirected to /[namespace]/[project]/branches/all

Edge: I want to clean up URLs for them afterwards (not mandatory on this MR). e.g.,

  • /[namespace]/[project]/branches?state=all => /[namespace]/[project]/branches/all
  • /[namespace]/[project]/branches?state=active => /[namespace]/[project]/branches/active
  • /[namespace]/[project]/branches?state=stale => /[namespace]/[project]/branches/stale
  • /[namespace]/[project]/branches?page=10 => /[namespace]/[project]/branches/all?page=10

Frontend (CSS): As Bootstrap 4 will not be introduced in the near future (#39086 (closed)), Panel component from Bootstrap 3 (obsoleted in BS4) is used in this MR.

Why was this MR needed?

There is some productivity degradation on handling/searching branches on a project with huge number of branches (100 or more).

Screenshots (if relevant)

branches-overview

Does this MR meet the acceptance criteria?

What are the relevant issue numbers?

Edited by Takuya Noguchi

Merge request reports