feat: add datacenter field to runners table #3016
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This was referenced Sep 29, 2025
Closed
|
Claude encountered an error —— View job I'll analyze this and get back to you. |
This was referenced Sep 29, 2025
Closed
Closed
commit: |
Graphite Automations"Test" took an action on this PR • (09/29/25)1 assignee was added to this PR based on Kacper Wojciechowski's automation. |
This was referenced Sep 29, 2025
NathanFlurry
approved these changes
Oct 1, 2025
Merge activity
|
graphite-app bot
pushed a commit
that referenced
this pull request
Oct 1, 2025
Closes FRONT-792 ### TL;DR Added a Datacenter column to the Runners Table to display runner datacenter information. ### What changed? - Added a new "Datacenter" column header to the Runners Table - Added a corresponding table cell in the RowSkeleton component to maintain proper layout when loading - Added a table cell to display the runner's datacenter value in the Row component ### How to test? 1. Navigate to the Runners Table view 2. Verify that the "Datacenter" column appears between the "Name" and "Slots" columns 3. Confirm that each runner's datacenter information is correctly displayed in the new column 4. Check that the loading skeleton properly includes the new column ### Why make this change? This change improves visibility of runner datacenter information, making it easier for users to identify where runners are located without having to drill down into individual runner details. This information is valuable for managing distributed runner deployments across multiple datacenters.
graphite-app
bot
deleted the
09-29-feat_add_datacenter_field_to_runners_table
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes FRONT-792
TL;DR
Added a Datacenter column to the Runners Table to display runner datacenter information.
What changed?
How to test?
Why make this change?
This change improves visibility of runner datacenter information, making it easier for users to identify where runners are located without having to drill down into individual runner details. This information is valuable for managing distributed runner deployments across multiple datacenters.