This repository has been archived by the owner on Mar 24, 2023. It is now read-only.
Ship release troubleshoot specs #981
Merged
Conversation
This file contains 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
laverya
approved these changes
Jun 20, 2019
emosbaugh
force-pushed
the
ship-release-troubleshoot-specs
branch
from
496e293 to
0761842
Compare
laverya
approved these changes
Jun 20, 2019
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
What I Did
How I Did it
Added collect and analyze spec to graphql ship release query
How to verify it
Integration test
Description for the Changelog
The promoted troubleshoot specs have been added to the ship state file
Picture of a Ship (not required but encouraged)