🪲 [Fix]: Multi-select custom properties no longer lose individual values#577
Draft
Marius Storhaug (MariusStorhaug) wants to merge 2 commits intomainfrom
Draft
🪲 [Fix]: Multi-select custom properties no longer lose individual values#577Marius Storhaug (MariusStorhaug) wants to merge 2 commits intomainfrom
Marius Storhaug (MariusStorhaug) wants to merge 2 commits intomainfrom
Conversation
Copilot started reviewing on behalf of
Marius Storhaug (MariusStorhaug)
April 5, 2026 11:18
View session
Contributor
Super-linter summary
All files and directories linted successfully For more information, see the GitHub Actions workflow run Powered by Super-linter |
Contributor
There was a problem hiding this comment.
Pull request overview
Fixes a bug in the repository custom properties model where multi-select custom property values returned as arrays by the GitHub API were being coerced into a single space-joined string, preventing correct downstream iteration.
Changes:
- Changed
GitHubCustomProperty.Valuefrom[string]to[object]to allow array values. - Updated the
GitHubCustomPropertyconstructor to detect non-string enumerables and cast them to[string[]].
Contributor
Super-linter summary
All files and directories linted successfully For more information, see the GitHub Actions workflow run Powered by Super-linter |
Contributor
Super-linter summary
All files and directories linted successfully For more information, see the GitHub Actions workflow run Powered by Super-linter |
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.
Multi-select custom property values are now correctly preserved as arrays. Previously, properties with multiple selections (e.g.,
["Custom Instructions", "License", "Prompts"]) were silently collapsed into a single space-joined string ("Custom Instructions License Prompts"), making it impossible to iterate over individual selections downstream.Fixed: Multi-select custom property values collapsed into a single string
Commands that return repository custom properties (such as
Get-GitHubRepositoryandGet-GitHubRepositoryCustomProperty) now preserve array values for multi-select properties. Each selection is available as a separate string element, so downstream logic that iterates over values works correctly.Single-select and text custom properties continue to work as before — their values remain plain strings.
Technical Details
GitHubCustomProperty.Valuetype changed from[string]to[object]to allow both scalar strings and string arrays.IEnumerable(excludingstring). If so, it casts to[string[]]; otherwise it assigns the value directly.