Skip to content

librarian: only generate changed APIs #818

@jskeet

Description

@jskeet

We're likely to start with a regeneration flow of "regenerate everything whether we think it's changed or not".

We might want to optimize this by checking for commits in the API paths since the last-generated-commit per library, and only regenerate a library if there are any such commits. (This is what v0.1.0 does, so the code should be easy to find.) That would also allow us to create a commit saying "I've regenerated libraries X, Y and Z" without having to detect which libraries have actually changed.

Currently setting as 0.2.0, but could easily move.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions