starred/panel
1
0
Fork 0
mirror of https://github.com/pelican-dev/panel.git synced 2026-02-24 11:20:41 +03:00
Code Issues 42 Packages Projects Releases 12 Wiki Activity

[PR #2014] [CLOSED] feat(activity-log): Add event-based icons to activity log entries #1702

New Issue
Closed
opened 2026-02-04 20:09:10 +03:00 by OVERLORD · 0 comments
OVERLORD commented 2026-02-04 20:09:10 +03:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/pelican-dev/panel/pull/2014
Author: @killerbite95
Created: 12/18/2025
Status: ❌ Closed

Base: main ← Head: main

📝 Commits (1)

  • 470e87b feat(activity-log): Add event-based icons to activity log entries

📊 Changes

1 file changed (+61 additions, -2 deletions)

View changed files

📝 app/Models/ActivityLog.php (+61 -2)

📄 Description

Summary

Previously, activity log icons only displayed the actor type (user, system, API). This change adds event-specific icons that match the panel's icon conventions used in SubuserPermission and other resources.

Changes

  • Add \EVENT_ICON_MAP\ constant with 18 event group mappings
  • Icons include: backup, file, database, schedule, allocation, startup, settings, subuser, console, control, power, sftp, server, auth, user, api-key, reset-password, ssh
  • Extract \getActorIcon()\ as fallback for unmapped events
  • Parse event string to determine group (e.g., \server:backup.create\ \ackup)

Benefits

  • Visual consistency with the rest of the panel
  • Better UX when browsing activity logs - users can quickly identify the type of action
  • Uses existing tabler icons already in use throughout the panel

Before/After

Before After
All entries show actor icon (user/system/api) Entries show event-specific icons (backup, database, file, etc.)

🔄 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/pelican-dev/panel/pull/2014 **Author:** [@killerbite95](https://github.com/killerbite95) **Created:** 12/18/2025 **Status:** ❌ Closed **Base:** `main` ← **Head:** `main` --- ### 📝 Commits (1) - [`470e87b`](https://github.com/pelican-dev/panel/commit/470e87bd4db6e076ae7b757ef66119318a7c4fdf) feat(activity-log): Add event-based icons to activity log entries ### 📊 Changes **1 file changed** (+61 additions, -2 deletions) <details> <summary>View changed files</summary> 📝 `app/Models/ActivityLog.php` (+61 -2) </details> ### 📄 Description ## Summary Previously, activity log icons only displayed the actor type (user, system, API). This change adds event-specific icons that match the panel's icon conventions used in SubuserPermission and other resources. ## Changes - Add \EVENT_ICON_MAP\ constant with 18 event group mappings - Icons include: backup, file, database, schedule, allocation, startup, settings, subuser, console, control, power, sftp, server, auth, user, api-key, reset-password, ssh - Extract \getActorIcon()\ as fallback for unmapped events - Parse event string to determine group (e.g., \server:backup.create\ \ackup\) ## Benefits - Visual consistency with the rest of the panel - Better UX when browsing activity logs - users can quickly identify the type of action - Uses existing tabler icons already in use throughout the panel ## Before/After | Before | After | |--------|-------| | All entries show actor icon (user/system/api) | Entries show event-specific icons (backup, database, file, etc.) | --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
OVERLORD added the pull-request label 2026-02-04 20:09:10 +03:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
not confirmed
pull-request
Mirrored from GitHub Pull Request
 👑 sponsor
💰 fund
🔴 hard
🟡 medium
🟡 medium
🟡 medium
🟢 easy
🟢 easy
🟢 easy
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
OVERLORD
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/panel#1702
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?