Skip to content

Health workflow: Mono repo commit message format #332

Open

Description

@dcharkes

mono_repo request: could we standardize on [pkg-name] XYZ for commit messages?

posted by @kevmoo

I think a check for this could fit well in the health workflow. cc @mosuem

Activity

  1. mosuem commented on Jan 2, 2025

    @mosuem
    Member

    We could add this check. I would be hesitant to add this for all dart-lang repos though, and we should probably have that discussion/decision first before doing the implementation work.

    cc @devoncarew

  2. devoncarew commented on Jan 2, 2025

    @devoncarew
    Contributor

    Hmm, we could dogfood something like this w/ an off-the shelf tool before doing something like adding it to the health checks. This could be via a git hook, or a github action (ala https://github.com/marketplace/actions/gs-commit-message-checker).

  3. devoncarew commented on Jan 2, 2025

    @devoncarew
    Contributor

    fwiw, I don't have a particular opinion about using package prefixes for commit messages, but haven't really given it any thought.

  4. dcharkes commented on Jan 2, 2025

    @dcharkes
    ContributorAuthor

    Hmm, we could dogfood something like this w/ an off-the shelf tool before doing something like adding it to the health checks. This could be via a git hook, or a github action (ala https://github.com/marketplace/actions/gs-commit-message-checker).

    Dogfooding on dart-lang/native as per:

  5. added
    type-questionA question about expected behavior or functionality
    on Nov 20, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    type-questionA question about expected behavior or functionality

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions