github.com/grantbow/fit@v0.7.1-0.20220916164603-1f7c88ac81e6/fit/warn-issues-dirty/Description (about)

     1  #### What did you do?
     2  $ bug
     3  
     4  #### What did you expect to see?
     5  
     6  it depends on how the team member uses git for issue and non-issues.
     7  
     8  manual git command `git status issues` will show changes in the filespec
     9  "issues" working directory without affecting the rest of the tree.
    10  
    11  it also depends on how the team member updates their issues.
    12  
    13  without a warn-issues-dirty feature, then when running bug or git commands
    14  there is no warning that the issues are dirty (updated or added).
    15  
    16  For examle, `bug create -n foo` will create the directory and touch Description
    17  but not add the Description file to the git staging area. Also as files under
    18  issues are updated or created these are not automatically added to the working
    19  directory. Updates are easier to catch along with other files already in git.
    20  Getting files into git requires something manual. This gets annoying when
    21  adding many different issue files like I have been doing with this program.
    22  
    23  Using `git add -A issues` correctly with a filespec will add all of these at
    24  one time. This assumes all edits under the issues directory should be staged.
    25  I sometimes leave files in my working directories so having a feature to warn
    26  me during `bug list` and perhaps elsewhere would help.
    27  
    28  
    29  #### What did you see instead?
    30  
    31  
    32  #### Does this issue reproduce with the latest release?
    33  
    34