Skip to content

Commit on exsisting PR #12

@Samq64

Description

@Samq64

If the previous translation PR hasn't been merged shouldn't the bot commit to the existing PR instead of creating a new one? It would cut down on the spam when they're not being merged for a week or two.

Related comment: ScratchAddons/ScratchAddons#7469 (comment)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions