Defining the Drupal 8 frontend gate

Created on 27 September 2018, over 6 years ago
Updated 28 May 2025, 27 days ago

Problem/Motivation

Core changes must pass through a series of "gates" to ensure their quality is up to standards. Gates are essentially "checklists" that can be used to evaluate a patch's readiness, by both developers and patch reviewers/core committers. The currently documented gates are missing frontend specific requirements for changes.

Proposed resolution

I've started preparing the frontend gates by documenting what the committer team has been enforcing for now.

🌱 Plan
Status

RTBC

Version

11.0 🔥

Component

other

Created by

🇫🇮Finland lauriii Finland

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • 🇳🇿New Zealand quietone

    Other than the improvements by xjm there hasn't been any work here for nearly 7 years. The Front End Gate documentation has been available since June 2022. Since there I haven't seen any request for improving the doc.

    The goal of this was to define the gate, and that has been done. Therefore, I think can be closed as fixed. Anyone can open a new issue to discuss improvements.

  • 🇫🇷France nod_ Lille

    yep, thanks!

  • 🇳🇿New Zealand quietone

    @nod_ Thanks.

    I've changed the status on the Front End gate to 'no know problems'.

    I am also adding credit for myself because I created the Front End Gate page back in June 2022 and then eventually followed up on this issue. It is an exception to do this but all the committers are quite busy now.

  • Automatically closed - issue fixed for 2 weeks with no activity.

Production build 0.71.5 2024