Update action for use with projectV2 #2
Merged
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
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.
GitHub recently announced a breaking change to the Projects API.
projectNextwill now beprojectV2, in addition to changes to how field values are passed in the mutation. This PR updates the action to use the new non-preview GraphQL Schema.One challenge, is that the
valuefield of the mutation must now be passed as a hash, with a different key depending on the field type. This is especially challenging because (A) GraphQL keys cannot be variables, and (B) the GitHub API does not accept hash variables. To get around this, I used Actions variable interpolation to modify the GraphQL query (key and variable type) to the appropriate field type and graphql variable type prior to passing the GraphQL query string to thegh apicommand. This metadata is pulled from the project object, so it should be a transparent and non-breaking change for existing implementations.You can see a successful run for multiple types of fields here.