Skip to content

Conversation

@BhaveshHeliconia
Copy link
Contributor

No description provided.

@github-actions
Copy link

There hasn't been any activity on this pull request in the past 4 months, so it has been marked as stale and it will be closed automatically if no further activity occurs in the next 30 days.
If you want this PR to never become stale, please ask a PSC member to apply the "no stale" label.

@github-actions github-actions bot added the stale PR/Issue without recent activity, it'll be soon closed automatically. label Aug 24, 2025
@BhaveshHeliconia BhaveshHeliconia force-pushed the 18.0-mig-pos_show_clock branch from 59e7c78 to 5d1f795 Compare August 25, 2025 06:40
@github-actions github-actions bot removed the stale PR/Issue without recent activity, it'll be soon closed automatically. label Aug 31, 2025
@github-actions
Copy link

github-actions bot commented Jan 4, 2026

There hasn't been any activity on this pull request in the past 4 months, so it has been marked as stale and it will be closed automatically if no further activity occurs in the next 30 days.
If you want this PR to never become stale, please ask a PSC member to apply the "no stale" label.

@github-actions github-actions bot added the stale PR/Issue without recent activity, it'll be soon closed automatically. label Jan 4, 2026
@BhaveshHeliconia BhaveshHeliconia force-pushed the 18.0-mig-pos_show_clock branch from 5d1f795 to 237c367 Compare January 5, 2026 03:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

stale PR/Issue without recent activity, it'll be soon closed automatically.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants