I originally thought that I could get away without having issue dependency fields for issues. However, something at work has convinced me that I do need them, so add them.
One interesting issue would be flattening the duplicate graph (and possibly also the dependency graph). Not flattening it would be easy, but less user friendly.
Support for this has been added. However, existing Nitpick repositories won't have all the metadata required to be compatible. The quickest way to solve the issue is to update the metadata of the issues outside Nitpick.
To do this you first need to write a small script such as:
#!/bin/bash
awk '/--/ {print "Depends_On:\nDuplicate_Of:";} {print}' $1 > $1.tmp
mv $1.tmp $1
I called this script add_fields.sh. Then in each of the project directories you can run the command:
find .nitpick -name issue -exec /path/to/add_fields.sh \{\} \;
After that is done you should test with Nitpick and if the issues load fine you can go ahead and commit this change manually.
I originally thought that I could get away without having issue dependency fields for issues. However, something at work has convinced me that I do need them, so add them.
Date: 2012-07-19 21:19:24
User: travisb
Through discussion with bug tracker users it would also be very useful to have automatically propagated duplicate bug metadata. So have that as well.
Date: 2012-07-20 03:02:02
User: travisb
One interesting issue would be flattening the duplicate graph (and possibly also the dependency graph). Not flattening it would be easy, but less user friendly.
Date: 2012-07-20 03:06:13
User: travisb
This has been left for
09100e3aDate: 2012-07-20 06:46:40
User: travisb
Support for this has been added. However, existing Nitpick repositories won't have all the metadata required to be compatible. The quickest way to solve the issue is to update the metadata of the issues outside Nitpick. To do this you first need to write a small script such as: #!/bin/bash awk '/--/ {print "Depends_On:\nDuplicate_Of:";} {print}' $1 > $1.tmp mv $1.tmp $1 I called this script add_fields.sh. Then in each of the project directories you can run the command: find .nitpick -name issue -exec /path/to/add_fields.sh \{\} \; After that is done you should test with Nitpick and if the issues load fine you can go ahead and commit this change manually.
Tracked by Nitpick