Skip to content

Avoid "empty" commits? #15

Open
Open

Description

@JulienPalard

Spotted "empty" commits like: 96e56e6 which just contains metadata update.

It would hurt python/docsbuild-scripts#171 by having /uk/ to rebuild even if not needed, consuming ~20mn of CPU each time.

Would it be possible to not commit those "non"-changes?

Activity

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

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions