Skip to content

[Copilot] Add conditional constraints enforcing the pairing rules between 'replace-upstream' and 'replace-reason' #178

Description

Issue Description

The source-files section in the TOMLs has the replace-upstream and replace-reason fields added in #171, which have a conditional dependency on each other encoded inside the configfile.go::validateReplaceUpstream function. That dependency is not encoded in the auto-generated JSON schema for the time being.

Expected Changes

Once #171 is merged, we'd like to update our JSON schema generation to reflect these conditional constraints.

Additional Context

No response

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

enhancementNew feature or request

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions