Open MarkW86 opened 3 weeks ago
stigzler
commented
1 week ago Investigated. This doesn't create a comment, but does create an action in the Issue history trail. There's possibly facility in Octokit to get this history, but could be a significant task as involves totally new view or significant modification of the comments view to intersperse historic actions with comment s history (as per GitHub's Issue page overview).
Will play around and determine timescale/do-ability.
stigzler
commented
1 week ago Two relative data types:
Event
TimelineEventInfo - this is preferable - seems to contain all info of above and more.
Relevant oktokit call:
gitHubClient.Issue.Timeline.GetAllForIssue(repositoryId, issueNumber);
Returns ReadOnlyList<TimeLineEventInfo>
Can get type of event from EventInfoState
How to intersperse Comments and Events? Separate tab? (looses value of chronologised actions)
Merge two collections of differing types: https://learn.microsoft.com/en-us/dotnet/desktop/wpf/data/how-to-implement-a-compositecollection?view=netframeworkdesktop-4.8&redirectedfrom=MSDN
😔 Gonna take some work. Will come back to it.
Make an issue in VisGit
Make a change to a versioned file
Go to the Git Changes window
enter in a comment for the commit with the last line reading #[X] where [X] is the name of the issue you made.
The above action will associate the commit with the issue on git once synced.
Go to GitHub, verify that the issue now has a comment related the commit you just made.
Go to VisGit and select the issue.
Note that there exists no comment or other content indicating a commit was related to this issue.
Restart Visual Studio
Note that the issue still exists.
I'd like to be able to see this type of update to an issue in VisGit. The commit has a comment directly related to the issue and IMHO constitutes a comment on the issue itself. Even with a refresh button or similar, I don't think VisGit supports displaying this type of change history on an issue. Please add! Many thanks :D