Add some issue and PR automatization

Author: dolfinus

.github/CODEOWNERS

@@ -0,0 +1,9 @@
+# See https://help.github.com/en/articles/about-code-owners
+# for details
+#
+# Maintainers are encouraged to use their best discretion in
+# setting reviewers on PRs manually, but this file should
+# offer a reasonable automatic best-guess
+
+# catch-all rule (this only gets matched if no rules below match)
+* @dolfinus

.github/lock.yml

@@ -0,0 +1,32 @@
+# Configuration for Lock Threads - https://github.com/dessant/lock-threads-app
+
+# Number of days of inactivity before a closed issue or pull request is locked
+daysUntilLock: 60
+
+# Skip issues and pull requests created before a given timestamp. Timestamp must
+# follow ISO 8601 (`YYYY-MM-DD`). Set to `false` to disable
+skipCreatedBefore: false
+
+# Issues and pull requests with these labels will be ignored. Set to `[]` to disable
+exemptLabels: ['enhancement', 'help wanted']
+
+# Label to add before locking, such as `outdated`. Set to `false` to disable
+lockLabel: ['outdated']
+
+# Comment to post before locking. Set to `false` to disable
+lockComment: false
+
+# Assign `resolved` as the reason for locking. Set to `false` to disable
+setLockReason: true
+
+# Limit to only `issues` or `pulls`
+# only: issues
+
+# Optionally, specify configuration settings just for `issues` or `pulls`
+# issues:
+#   exemptLabels:
+#     - help-wanted
+#   lockLabel: outdated
+
+# pulls:
+#   daysUntilLock: 30

.github/no-response.yml

@@ -0,0 +1,11 @@
+# Configuration for probot-no-response - https://github.com/probot/no-response
+
+# Number of days of inactivity before an Issue is closed for lack of response
+daysUntilClose: 30
+# Label requiring a response
+responseRequiredLabel: awaiting response
+# Comment to post when closing an Issue for lack of response. Set to `false` to disable
+closeComment: >
+    This issue has been automatically closed because it has been awaiting a response for too long.
+    When you have time to to work with the maintainers to resolve this issue, please post a new comment and it will be re-opened.
+    If the issue has been locked for editing by the time you return to it, please open a new issue and reference this one. Thank you for taking the time to improve setuptools-git-versioning!