+ [2019-04-08T13:26:54Z] Crizzo i like to add a direcotory to .gitignore, without one file in it
+ [2019-04-08T13:27:03Z] Crizzo like: /foo/ should be ignore
+ [2019-04-08T13:27:15Z] Crizzo except: foo/bla.txt
+ [2019-04-08T13:29:16Z] Crizzo should be /foo/
+ [2019-04-08T13:29:26Z] Crizzo !/foo/bla.txt

message no. 171516

Posted by circuitbone in #github at 2019-04-08T00:09:35Z

choice https://help.github.com/en/articles/adding-a-new-ssh-key-to-your-github-account . no one sticks around for the answers.
+ [2019-04-09T01:47:05Z] redrambles Hello! A few of us maintain a public repository that we use to teach beginners how to get started with Git. It's a very small project. Students basically need to submit a pull request - and if it meets X criteria, we accept it. Over the last few days, we noticed that someone who isn't at all involved (not a student, not a mentor) has been commenting on a bunch of the pull requests, which has never happened before. The
+ [2019-04-09T01:47:05Z] redrambles comments aren't terrible or anything - just out of left field and confusing. Aside from making the repository private, what options (if any) do we have?
+ [2019-04-09T01:51:08Z] Infininight redrambles: You can ban a user on the organization level
+ [2019-04-09T01:51:28Z] Infininight here: https://github.com/organizations/foo/settings/user_blocks
+ [2019-04-09T01:51:38Z] redrambles @Infininight, thank you