microsoft / microsoft/azure-linux-dev-tools
[Copilot] Add conditional constraints enforcing the pairing rules between 'replace-upstream' and 'replace-reason'
Open
@liunan-ms is already working on this.
Since Sep 8, 2026.
enhancement
- Dominant language
- Go
- Stars
- 18
- Forks
- 27
- Avg merge
- 4d 33m
- Merged PRs (30d)
- 24
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_
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.