Adam Altman

Can you tell us about your use case a bit more? How come so many repos that automation is required?

> **Describe alternatives tried** > I'm new at this, so I'm open to suggestions. I'm aware that it's entirely possible that I'm looking at this completely wrong. I want to...

> Also, we may need to add `files` config to the `redocly.yaml`. What possible configurations are there? Defining a list of files so that the argument can be avoided?

I opened a can of worms. 🪱 🪱 It could also be a list of folders. ```yaml files: - ./xray - ./zebra ``` Also, are they with or without trailing...

I thought we had `no-sibling-refs` rule, but I cannot find it.

We're getting closer to a release candidate.

This issue should be replaced by this: 1. Add support for 3 additional locator properties: `filterInParentKeys`, `filterOutParentKeys`, `matchParentKeys` (regex). 2. Change `context` to `if`. 3. Change `if` list to conform...

This is incorrect: ``` type: object properties: companyId: required: true type: number ``` Do this instead: ``` type: object required: - companyId properties: companyId: type: number ``` Let's leave this...

Strange? I'll leave that to the community to decide. Different between parameters and schemas? Yes! You got it exactly: ``` parameters: filter: required: true # ... # schemas set required...

I'm not sure. It can be valid and not full, right?