To: mad-issues@mit.edu
Cc: Oliver Thomas othomas@mit.edu
Reply-To:
From: Oliver Thomas othomas@mit.edu
Date: Wed, 9 Oct 2024 14:25:46 +0000
Issues in the MITProjectManus/MAD-Issues GitHub repo can now be opened via email to mad-issues@mit.edu. This works via a Zapier automation and a cryptic Zapier email that has been added to the mailing list. It can be changed if the Zapier message gets out and spammed.
The process @murph234 and @othomasprime are thinking of is that end-user reported issues will be kept in the MAD-Issues repo, and related issues (one or more per end-user reported issue depending on assessment) will be added to the actual code repos and referenced in a comment on the end-user reported issue. (I don't know if AT mentions work in the email body for a Zapier integration but trying it out here. -othomas)
Oliver
To: mad-issues@mit.edu
Cc: Oliver Thomas othomas@mit.edu
Reply-To:
From: Oliver Thomas othomas@mit.edu
Date: Wed, 9 Oct 2024 14:25:46 +0000
Issues in the MITProjectManus/MAD-Issues GitHub repo can now be opened via email to mad-issues@mit.edu. This works via a Zapier automation and a cryptic Zapier email that has been added to the mailing list. It can be changed if the Zapier message gets out and spammed.
The process @murph234 and @othomasprime are thinking of is that end-user reported issues will be kept in the MAD-Issues repo, and related issues (one or more per end-user reported issue depending on assessment) will be added to the actual code repos and referenced in a comment on the end-user reported issue. (I don't know if AT mentions work in the email body for a Zapier integration but trying it out here. -othomas)
Oliver