Commit message convention

Open
#800 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
25/100
Issue type
Documentation
Clarity
Needs clarification
Activity status
Stale
Tech stack
git
Domain
documentation

Research direction

Read the linked Chris Beams commit-message guide and inspect this repository’s contributor documentation for any existing commit conventions. Identify where a project-wide convention should be recorded; done means the chosen guidance is documented consistently for contributors.

Written by the indexing model from the issue text.

Description

enhancement help wanted question

Can we follow https://chris.beams.io/posts/git-commit/ to unify the commit message style?

It'll be good to follow a styling guide, just like coding style.

cc @nodejs/docker

Dominant language
Dockerfile
Stars
8.6k
Forks
2k
Avg merge
10h 19m
Merged PRs (30d)
16

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from nodejs/docker-node

All issues in nodejs/docker-node

Similar issues

More Documentation issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.