Repository navigation
Write an audit log #4
Description
Activity
👍 This is something I was really pondering. Also- public visibility? I would lean towards yes- but I guess it depends on what is logged. For an example, see the thoughts here: nodejs/inclusivity#85 (comment)
I agree with public visibility when we've had the chance to look at output ourselves. This would involve things like changes to memberships too. We likely need to look at all data and draw a line.
As for making this persistent I guess the choice lies with the person that opens the PR, but personally I'd be keen on using postgres over stuff like mongodb.
+1 for postgres. Worth mentioning I think the most important thing is how easy and well suited the db is for querying for insights later, not necessarily if it's easy to insert data.
This is more than 8 years idle and we've gotten by with the GitHub audit log, so I'm going to close this. But if someone feels like it should remain open or is interested in doing the work, please re-open, comment, or open a new issue.
Write a log of all commits, opening/closing pr's, etc so we can track whether malicious commits or force pushes were made in case of an incident.