@GusRiva and I were chatting about ways of properly documenting that an issue has been (or is in the process of being) discussed by council (during a F2F or in regular meetings) -- while we do often summarize results of a discussion, those comments do not replicate the full scope of the discussion, which is detailed much more expansively in the minutes. However, it's not always clear which issues have been mentioned in the minutes.
Now that the minutes are all going to be in Markdown, we think that there could be a way to automate a kind of notification system that a ticket was indeed discussed; maybe a GitHub action that runs on a new document and writes a comment on each issue? Or does it create an issue (in what repo?) that simply lists it?
@GusRiva and I were chatting about ways of properly documenting that an issue has been (or is in the process of being) discussed by council (during a F2F or in regular meetings) -- while we do often summarize results of a discussion, those comments do not replicate the full scope of the discussion, which is detailed much more expansively in the minutes. However, it's not always clear which issues have been mentioned in the minutes.
Now that the minutes are all going to be in Markdown, we think that there could be a way to automate a kind of notification system that a ticket was indeed discussed; maybe a GitHub action that runs on a new document and writes a comment on each issue? Or does it create an issue (in what repo?) that simply lists it?