#Doing a pass at improving our codege CI
1 messages · Page 1 of 1 (latest)
Changeset is fun to use once you get the hang of it. Let's see how well it works end-to-end!
Our docs module has Lint function that is QUITE the kitchen sink:
- Actually lint the markdown
- Check that generated docs are up to date (not really linting but ok)
- Check that the site builds (seems excessive)
- Check that the repo's generated Changelog is up-to-date? (why?)
<@&946480760016207902>
@lime thicket dilemna in dagger call sdk all generate -> it fans out to each SDK's Generate() function, and returns the merged result.
PROBLEM: you can merge directories, but not Changesets. So either:
- I change
sdk all generateto return a[]*Changeset(but then it won't apply)
or 2) I changesdk all generateto take asourceargument, and apply all the changes to that, then returnChangeset
or 3) we add aChangeset.withChanges()or equivalent, to merge multipleChangesets
As usual, touching our SDK CI is a nightmare
i would really like to be able to merge ChangeSets
but, one thing to consider - if I merge a ChangeSet, then it suddenly might have multiple origins