Skip to content

Commit 786a2d1

Browse files
owenniblockCopilot
andcommitted
Shorten FeatureFlagIssueFieldsMultiSelect doc comment
Match the style of the other flag constants in this file. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
1 parent 83a4a32 commit 786a2d1

1 file changed

Lines changed: 1 addition & 11 deletions

File tree

pkg/github/feature_flags.go

Lines changed: 1 addition & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -17,17 +17,7 @@ const FeatureFlagIFCLabels = "ifc_labels"
1717
const FeatureFlagFileBlame = "file_blame"
1818

1919
// FeatureFlagIssueFieldsMultiSelect is the feature flag name for the multi-select
20-
// variant of the custom issue fields write surface. When enabled, issue_write,
21-
// set_issue_fields, and list_issues accept multi-select inputs
22-
// (`field_option_names`, `multi_select_option_ids`, and `field_filters[].values`
23-
// respectively) and their descriptions advertise multi-select. When disabled, the
24-
// legacy variants of those tools are served, which do not accept multi-select
25-
// inputs and whose descriptions do not mention multi-select.
26-
//
27-
// The flag is intentionally write-surface-only — read paths (list_issue_fields,
28-
// issue_read, list_issues enrichment) continue to surface multi-select field
29-
// VALUES for orgs that have dotcom-side multi-select enabled, matching what the
30-
// dotcom UI already shows.
20+
// variant of the consolidated issue-fields write tools (issue_write, list_issues).
3121
const FeatureFlagIssueFieldsMultiSelect = "remote_mcp_issue_fields_multiselect"
3222

3323
// AllowedFeatureFlags is the allowlist of feature flags that can be enabled

0 commit comments

Comments
 (0)