Closed djmitche closed 3 years ago
The reason I suggested description_length
rather than body_length
was for consistency with our existing configuration options (such as annotation_length
) which reference fields in terms of the field names in taskwarrior rather than in their respective services. What do you think?
Description isn't task field, though. I was keying off the name of the uda. I can change it if you'd like, though.
On Mon, Nov 30, 2020, 12:27 AM ryneeverett notifications@github.com wrote:
The reason I suggested description_length rather than body_length was for consistency with our existing configuration options (such as annotation_length) which reference fields in terms of the field names in taskwarrior rather than in their respective services. What do you think?
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/ralphbean/bugwarrior/pull/782#issuecomment-735554429, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAAHAAPJFWKJ4X26Z32JNE3SSMUMRANCNFSM4UGR2SIQ .
Oh, also, github.description_length
applies to the task description, rather than the issue description, so I think re-using the word description
in this context would be super-confusing.
Nevermind, it was I that was confused. This makes sense.
This controls the maximum length of the githubbody UDA, and can be used to avoid syncing the body at all (by setting it to 0).
Fixes #766.