Skip to content

Update Security template guidance to prefer components over templates

Problem to solve

After the launch of cicomponents, the sectionsec has been slow to prioritize component adoption over the legacy template usage. While the usage and capabilities vary, the future of CI configuration leans towards components and we should align with the rest of the company direction.

Proposal

Prework

  1. Evaluate whether templates can be completely replaced with components
  2. Resolve drift between templates and components

Unification timeline

  1. Update sec analyzer configuration documentation to prefer CI components over templates
  2. Establish unification timeline
  3. Consider monitoring template usage to adjust deprecations around existing users

Auto-Summary 🤖

Discoto Usage

Points

Discussion points are declared by headings, list items, and single lines that start with the text (case-insensitive) point:. For example, the following are all valid points:

  • #### POINT: This is a point
  • * point: This is a point
  • + Point: This is a point
  • - pOINT: This is a point
  • point: This is a **point**

Note that any markdown used in the point text will also be propagated into the topic summaries.

Topics

Topics can be stand-alone and contained within an issuable (epic, issue, MR), or can be inline.

Inline topics are defined by creating a new thread (discussion) where the first line of the first comment is a heading that starts with (case-insensitive) topic:. For example, the following are all valid topics:

  • # Topic: Inline discussion topic 1
  • ## TOPIC: **{+A Green, bolded topic+}**
  • ### tOpIc: Another topic

Quick Actions

Action Description
/discuss sub-topic TITLE Create an issue for a sub-topic. Does not work in epics
/discuss link ISSUABLE-LINK Link an issuable as a child of this discussion

Last updated by this job

Discoto Settings 
---
summary:
  max_items: -1
  sort_by: created
  sort_direction: ascending

See the settings schema for details.

Edited by 🤖 GitLab Bot 🤖