Skip to content

librarian: design a fallback if release PR body is too big #2543

@codyoss

Description

@codyoss

We have couple issues now related to the PR body being too big: #2525, #2470, and #2321. This problem seems to be mitigated on the generate side now that we batch similar messages together, but this is still an issue on the release side of things. We need a way to significantly reduce the PR Body size if multiple(all) libraries are being updated or we need an overflow handling mechanism.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions