You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've realised most of the personal logging I want to do are things I'm pushing out to social media already. Consequently, I want a frictionless logging classifier. The rule is simple:
If I see a status (Measurement::Social) containing the #log tag, then add that to my personal log. (Possibly with a note indicating its source).
---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/1927389-personal-log-classifying-agent?utm_campaign=plugin&utm_content=tracker%2F347315&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F347315&utm_medium=issues&utm_source=github).
The text was updated successfully, but these errors were encountered:
The default strings generated by BugWarrior for github use a short 'PR'
or 'Is' string to indicate if something is a pull-request or issue
respectively. However no UDA exists allowing the user to use these when
specifying their own description_templates in their `.bugwarriorrc`.
This change adds a `githubshorttype` UDA.
Sample config:
description_template = {{githubrepo}}#{{githubnumber}} ({{githubshorttype}}) {{githubtitle}}
Snippet of resulting output (dry-run):
INFO:bugwarrior.db:Adding task pjf/exobrain#50 (Is) Personal log classifying agent (not really)
INFO:bugwarrior.db:Adding task pjf/masterwork-dwarf-fortress#122 (Is) Wild orc traders keep bringing barrels of fire (not really)
INFO:bugwarrior.db:Adding task pjf/exobrain#55 (PR) Logging (not really)
INFO:bugwarrior.db:Adding task pjf/masterwork-dwarf-fortress#125 (Is) Simple wood option doesn't apply to orcs. (not really)
INFO:bugwarrior.db:Adding task Dual-Life/autodie#51 (PR) POD update (not really)
I've realised most of the personal logging I want to do are things I'm pushing out to social media already. Consequently, I want a frictionless logging classifier. The rule is simple:
The text was updated successfully, but these errors were encountered: