Update 'tiger service fork' to output service info like 'tiger servic…#40
Merged
nathanjcochran merged 1 commit intomainfrom Oct 4, 2025
Merged
Update 'tiger service fork' to output service info like 'tiger servic…#40nathanjcochran merged 1 commit intomainfrom
nathanjcochran merged 1 commit intomainfrom
Conversation
murrayju
approved these changes
Oct 4, 2025
Member
murrayju
left a comment
murrayju
left a comment
There was a problem hiding this comment.
Thanks. I had actually intended to do this in my PR, but then lost track of it.
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Updates
tiger service forkto output the service info in the same way thattiger service createwas updated to return it in #32.Note that there is currently some information missing from the output. I believe it's ultimately because the GraphQL query for making a fork is requesting different fields in the response than the GraphQL query for creating a service. I mentioned this before here, and it sounds like we will probably just update the create service and fork service REST API endpoints to use the same GraphQL query under the hood (they're both technically using the same
createServicemutation, and both already take aforkConfig). I plan to tackle that next week. UPDATE: fixed here.