github.com/quay/claircore@v1.5.28/docs/contributor/commit-style.md (about)

     1  # Commit Style
     2  
     3  The Claircore project utilizes well structured commits to keep the history useful and help with release automation.
     4  We suggest signing off on your commits as well.
     5  
     6  A typical commit will take on the following structure:
     7  
     8  ```
     9  <scope>: <subject>
    10  
    11  <body>
    12  Fixes #1
    13  Pull Request #2
    14  
    15  Signed-Off By: <email>
    16  ```
    17  
    18  The header of the commit is regexp checked before commit and your commit will be kicked back if it does not conform.
    19  
    20  ## Scope
    21  
    22  This is the section of code this commit influences. 
    23  
    24  You will often see scopes such as "notifier", "auth", "chore", "cicd".
    25  
    26  ## Subject
    27  
    28  Subject is a short and concise summary of the change the commit is introducing. It should be a sentence fragment without starting capitalization and ending punctuation and limited to about 60 characters, to allow for the scope prefix and decoration in the git log.
    29  
    30  ## Body
    31  
    32  Body should be full of detail.
    33  
    34  Explain what this commit is doing and why it is necessary.
    35  
    36  You may include references to issues and pull requests as well.