One thing I often wish Fossil did was show other things (tickets, wiki pages) that reference tickets rather than just checkins -- I often have a mess of tickets that refer to other tickets and no place to generate a list of them, or reverse them.

On Wed, 13 Dec 2017, Richard Hipp wrote:

On 12/13/17, jungle Boogie <[email protected]> wrote:
On 13 December 2017 at 09:07, Warren Young <[email protected]> wrote:
On Dec 13, 2017, at 9:55 AM, Richard Hipp <[email protected]> wrote:

Would Git or GitHub have told me about those prior tickets?

GitHub is pretty good about surfacing such information, as long as the
ticket references the checkin ID.

Yep. With most projects I follow on github, the commiter includes the
referenced issue number in the description or somewhere in the commit
message.

Is the ticket number included in the check-in that *fixed* the issue,
or in the check-in that *caused* the issue.  Therein lays the
difference.  I wasn't looking that one of the check-ins that fixed the
bug - I was looking at the check-in that caused the bug, and it
referred me forward to issues that happened in the future.

Maybe GitHub will do that?  Do you have an example?
--
D. Richard Hipp
[email protected]
_______________________________________________
fossil-users mailing list
[email protected]
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

_______________________________________________
fossil-users mailing list
[email protected]
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Reply via email to