Skip to content

chore(connectors): generate remaining config schema#6680

Draft
xfournet wants to merge 60 commits into
masterfrom
oob/generate_remaining_config_schema
Draft

chore(connectors): generate remaining config schema#6680
xfournet wants to merge 60 commits into
masterfrom
oob/generate_remaining_config_schema

Conversation

@xfournet

@xfournet xfournet commented Jun 9, 2026

Copy link
Copy Markdown
Member

Proposed changes

Related issues

Checklist

  • I consider the submitted work as finished
  • I have signed my commits using GPG key.
  • I tested the code for its functionality using different use cases
  • I added/update the relevant documentation (either on github or on notion)
  • Where necessary I refactored code to improve the overall quality

xfournet added 30 commits June 8, 2026 09:38
@Filigran-Automation Filigran-Automation changed the title [draft] remaining config schema chore(connectors): generate remaining config schema Jun 9, 2026
@Filigran-Automation Filigran-Automation added the filigran team Item from the Filigran team. label Jun 9, 2026
@Filigran-Automation

Copy link
Copy Markdown
Member

🤖 [AI-generated]

Hey @xfournet! 👋 Thanks a lot for opening PR #6680 — that's a big, valuable batch of config-schema work across all those connectors, really appreciate it! 🙏

I just had a quick look and I think the description could be enhanced a little to help reviewers get through it faster. I haven't changed anything in your description — just a gentle, optional suggestion:

Area What could help Suggestion
### Related issues The section is empty, so the PR isn't linked to a tracking issue (and the title convention expects a (#issue) reference) Add the associated issue with a closing keyword, e.g. Closes #1234
### Proposed changes A single line covers a fairly large change set (119 files), which is a lot of context for reviewers to reconstruct A couple of bullets on what's generated/migrated and why would make review much smoother

💡 If helpful, the contribution guide walks through what to include (it notes every PR should be linked to a GitHub issue describing its purpose).

No rush at all — and no worries if some of this is still in flight while it's a draft. Thanks again for the contribution! 🚀

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

Labels

filigran team Item from the Filigran team.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants