Edgewall Software

Changes between Version 17 and Version 18 of TracDev/DevelopmentWorkflow


Ignore:
Timestamp:
Apr 27, 2020, 7:50:09 PM (5 months ago)
Author:
Ryan J Ollos
Comment:

Document [skip ci].

Legend:

Unmodified
Added
Removed
Modified
  • TracDev/DevelopmentWorkflow

    v17 v18  
    1717Commits should be atomic. If three separate issues are being fixed (unless they are all fixed by one change), they need to be done as three separate commits. This also applies to whitespace and style changes, which should be done in their own commit. Whitespace commits should not include code or content changes. Accordingly, code change commits should not include whitespace changes (unless the whitespace changes are on the same lines as the code being changed).
    1818
    19 Commit messages should describe what changed, and reference the issue number if the commit closes or is associated with a particular issue. Example:
     19Commit messages should describe what changed, and reference the issue number if the commit closes or is associated with a particular issue.
    2020
     21Example:
    2122{{{
    2223Version: Short Description
    2324 
    2425Optional Long Description
    25  
     26
     27[skip ci] (optional)
     28
    2629Refs #zzz
    2730}}}
     
    3437
    3538There are two line breaks between the subject and the long description. The description can have any length and formatting, like lists, but it must be hard-wrapped at 80 characters.
     39
     40=== Skipping Build
     41
     42If you are confident the CI tests don't need to be
     43run for this commit (e.g. a documentation change),
     44add [[https://docs.travis-ci.com/user/customizing-the-build/#skipping-a-build|"[skip ci]"]].
    3645
    3746=== References