#Vs code smart reminder how to#

We can also use automated commenting for the same purpose. That way we would know after what date we would be able to mark the project unsupported. I think putting a marker would be good, but it would be best to have a 'last contacted' field that shows on which date a reminder was sent to the maintainer. Test This is another test security issue Īdded a line break and posting example without code for wrapping If you do not feel able to resolve the issue within the two-week timeframe please stay in communication so that the security team can coordinate with you about any additional time you may need. If you are unresponsive during this two week period, the security team may opt to publish a security advisory recommending that the affected module be uninstalled. Please login into within 2 weeks and provide an update. These issues are posted to - a private issue queue for you to coordinate with the security team as you develop a solution for the vulnerability and draft a security advisory. There are security issues for projects that you maintain that are awaiting your action. Output on my local looks like this: Hello demo, Here is a hacky attempt at providing this in an existing drush file. If you do not feel able to resolve the issue within the two-week timeframe please stay in communication so that the security team can coordinate with you about any additional time you may need.įor more information on your responsibilities as a maintainer contacted by the security team, please see: These issues are posted to – a private issue queue for you to coordinate with the security team as you develop a solution for the vulnerability and draft a security advisory.

This is just a rough attempt at doing that, likely needs additional finesse from someone on the security team: Hello XXX, We should also link to: for a more detailed explanation.

#Vs code smart reminder how to#

Explain what to do if the maintainer doesn't know how to respond/fix the issue.

Explain the consequences of not responding.

My suggestion is to provide a little bit more in-context explanation as to why we're asking the maintainer to respond within a particular timeframe.