Budget analysis

[lhaze]

We're already looking for time entries in the repository. Now let's add the other end of the time-tracking: budget entries. These look like one of the below:

• :dart: 5d # => 🎯 5d
• :dart: 5d | We cannot go over this time at all! # => 🎯 5d | We cannot go over this time at all!

These entries might be given to a milestone or issue description or added to an issue comment. The logic of adding (or not) entries is prolly common to special cases of summing up time entries and will be discussed in separate issue.

• Budget entry seeking
• Seeking more than one entry in the same message
• Budget entries in responses from the core

Questions:

• Q: Does time entry and budget entry in the SAME issue description/comment make sense? A: Probably yes, though it seems like a loooong shortcut from budgeting to budget execution by ONE man.

[ffigiel]

Suppose we have this situation:

1. an issue is created with 🎯 4h
2. a commit linking to that issue is created, along with some time entry
3. a comment is added to an issue, with 🎯 2h

Question: Did the target change? or is this a separate target?
Let's add point 4: a new commit is then added.
Does it refer to target 1 or target 2? The committer might not have known about the new target. This ambiguity hints that the most sane interpretation is "target has changed".