About the "NPC" Tag

To clearly trace the source of operations, Cloud Native Build strictly distinguishes between user UI interactions and automated non-UI interactions (such as triggering automated pipelines or calling OpenAPIs).

In Cloud Native Build, user automated non-UI interactions are collectively referred to as NPC actions, and the operator identity is displayed as NPC.

💡 UI Examples

Taking Issue comments as an example, the visual distinction is as follows:

NPC Comment

Human Comment

🏷️ Detailed Rules

1. Difference Between Operations

• No Tag (Normal Operation): Represents "Manual Operation". These are actions performed directly by you (or your account) via the web interface (e.g., clicking buttons, filling forms).

• NPC Tag (Non-UI Operation): Represents "Non-Direct UI Operation". These are changes not manually triggered via the current web interface but completed by "background" mechanisms.

2. Common "NPC" Scenarios

Records with the NPC tag usually originate from:

• Automation Tools: e.g., Adding comments via pipeline builds, automated bot replies.
• OpenAPI Calls: Triggering Cloud Native Build via third-party integration tools or scripts.
• System Processing: e.g., Data synchronization triggered by cron jobs, auto-archiving.

Summary: If you see NPC, it means the update was completed in the background by a system, API, or tool, rather than by a manual user action on the screen.