[PR #22049] docs: Add component specification and usage examples for N8nBadge #22013

Open
opened 2025-11-20 06:22:40 -06:00 by GiteaMirror · 0 comments
Owner

📋 Pull Request Information

Original PR: https://github.com/n8n-io/n8n/pull/22049
Author: @cstuncsik
Created: 11/19/2025
Status: 🔄 Open

Base: masterHead: ds-340-write-badge-api-specs


📝 Commits (2)

  • 93609e5 docs: Add component specification and usage examples for N8nBadge
  • 859aea6 Merge branch 'master' into ds-340-write-badge-api-specs

📊 Changes

1 file changed (+220 additions, -0 deletions)

View changed files

packages/frontend/@n8n/design-system/src/v2/components/Badge/component-badge.md (+220 -0)

📄 Description

Summary

Review / Merge checklist

  • PR title and summary are descriptive. (conventions)
  • Docs updated or follow-up ticket created.
  • Tests included.
  • PR Labeled with release/backport (if the PR is an urgent fix that needs to be backported)

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/n8n-io/n8n/pull/22049 **Author:** [@cstuncsik](https://github.com/cstuncsik) **Created:** 11/19/2025 **Status:** 🔄 Open **Base:** `master` ← **Head:** `ds-340-write-badge-api-specs` --- ### 📝 Commits (2) - [`93609e5`](https://github.com/n8n-io/n8n/commit/93609e5dcbbeaa3fd997e70aac882e9f565b4c7c) docs: Add component specification and usage examples for N8nBadge - [`859aea6`](https://github.com/n8n-io/n8n/commit/859aea6a39ec49854d9db9373c9e0fac8bef0666) Merge branch 'master' into ds-340-write-badge-api-specs ### 📊 Changes **1 file changed** (+220 additions, -0 deletions) <details> <summary>View changed files</summary> ➕ `packages/frontend/@n8n/design-system/src/v2/components/Badge/component-badge.md` (+220 -0) </details> ### 📄 Description ## Summary <!-- Describe what the PR does and how to test. Photos and videos are recommended. --> ## Related Linear tickets, Github issues, and Community forum posts <!-- Include links to **Linear ticket** or Github issue or Community forum post. Important in order to close *automatically* and provide context to reviewers. https://linear.app/n8n/issue/ --> <!-- Use "closes #<issue-number>", "fixes #<issue-number>", or "resolves #<issue-number>" to automatically close issues when the PR is merged. --> ## Review / Merge checklist - [ ] PR title and summary are descriptive. ([conventions](../blob/master/.github/pull_request_title_conventions.md)) <!-- **Remember, the title automatically goes into the changelog. Use `(no-changelog)` otherwise.** --> - [ ] [Docs updated](https://github.com/n8n-io/n8n-docs) or follow-up ticket created. - [ ] Tests included. <!-- A bug is not considered fixed, unless a test is added to prevent it from happening again. A feature is not complete without tests. --> - [ ] PR Labeled with `release/backport` (if the PR is an urgent fix that needs to be backported) --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
GiteaMirror added the
pull-request
label 2025-11-20 06:22:40 -06:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/n8n#22013
No description provided.