Merge pull request #62 from hsf-training/update-config-file-stale-bot

Update stale bot configuration

Author: michmx

.github/config.yml

@@ -0,0 +1,31 @@
+# === IMPORTANT: CENTRALLY MAINTAINED FILE ===
+# This file was automatically added via the scripts at the maintenance repository.
+# Please do not change it. Rather, update the blueprint in the maintenance repository and propagate
+# the changes from there.
+# IF YOU REALLY WANT TO MAKE REPOSITORY SPECIFIC CHANGES TO THIS FILE, PLEASE REMOVE THIS NOTICE!
+# Tag @klieret for any questions.
+# ======
+
+# Configuration for welcome - https://github.com/behaviorbot/welcome
+
+# Configuration for new-issue-welcome - https://github.com/behaviorbot/new-issue-welcome
+
+# Comment to be posted to on first time issues
+newIssueWelcomeComment: >
+  Thanks for opening your first issue here 💖! If you have any questions, feel free to mention one of the conveners, previous contributors, or attend our weekly meeting (see https://hepsoftwarefoundation.org/workinggroups/training.html).  Also, sometimes issues go unnoticed, so don't hesitate to @mention some of us, if we do not come back to you within a few days.
+
+# Configuration for new-pr-welcome - https://github.com/behaviorbot/new-pr-welcome
+
+# Comment to be posted to on PRs from first time contributors in your repository
+newPRWelcomeComment: >
+  Thanks for opening your first pull request here 🚀! If you have any questions, feel free to mention one of the conveners, previous contributors, or attend our weekly meeting (see
+   [our homepage](https://hepsoftwarefoundation.org/workinggroups/training.html)).  Also, sometimes PRs go unnoticed, so don't hesitate to @mention some of us, if we do not come back to you within a few days.
+
+# Configuration for first-pr-merge - https://github.com/behaviorbot/first-pr-merge
+
+# Comment to be posted to on pull requests merged by a first time user
+firstPRMergeComment: >
+  Congrats on merging your first pull request 🎉! We greatly appreciate it.
+
+  You might be eligible to be added to the [HSF Training Community](https://hepsoftwarefoundation.org/training/community_by_year) page (see the instructions on the page for how to create a profile). If you already have created a profile previously, make sure you're also added to the current year.
+  If this repository features a list of contributors at the bottom of the readme, you might also be eligible to add yourself there.

.github/stale.yml

@@ -0,0 +1,69 @@
+# === IMPORTANT: CENTRALLY MAINTAINED FILE ===
+# This file was automatically added via the scripts at the maintenance repository.
+# Please do not change it. Rather, update the blueprint in the maintenance repository and propagate
+# the changes from there.
+# IF YOU REALLY WANT TO MAKE REPOSITORY SPECIFIC CHANGES TO THIS FILE, PLEASE REMOVE THIS NOTICE!
+# Tag @michmx for any questions.
+# ======
+
+# Configuration for probot-stale - https://github.com/probot/stale
+
+# Number of days of inactivity before an Issue or Pull Request becomes stale
+daysUntilStale: 60
+
+# Number of days of inactivity before an Issue or Pull Request with the stale label is closed.
+# Set to false to disable. If disabled, issues still need to be closed manually, but will remain marked as stale.
+daysUntilClose: false
+
+# Only issues or pull requests with all of these labels are check if stale. Defaults to `[]` (disabled)
+onlyLabels: []
+
+# Issues or Pull Requests with these labels will never be considered stale. Set to `[]` to disable
+exemptLabels:
+  - pinned
+  - security
+  - "[Status] Maybe Later"
+
+# Set to true to ignore issues in a project (defaults to false)
+exemptProjects: false
+
+# Set to true to ignore issues in a milestone (defaults to false)
+exemptMilestones: false
+
+# Set to true to ignore issues with an assignee (defaults to false)
+exemptAssignees: false
+
+# Label to use when marking as stale
+staleLabel: stale
+
+# Comment to post when marking as stale. Set to `false` to disable
+markComment: >
+  This issue or pull request  has been automatically marked as stale because it has not had
+  recent activity. Please manually close it, if it is no longer relevant,
+  or ask for help or support to help getting it unstuck.
+  Let me bring this to the attention of @amorenobr @vlukashenko @richa2710 @michmx for now.
+
+# Comment to post when removing the stale label.
+# unmarkComment: >
+#   Your comment here.
+
+# Comment to post when closing a stale Issue or Pull Request.
+# closeComment: >
+#   Your comment here.
+
+# Limit the number of actions per hour, from 1-30. Default is 30
+limitPerRun: 30
+# Limit to only `issues` or `pulls`
+# only: issues
+
+# Optionally, specify configuration settings that are specific to just 'issues' or 'pulls':
+# pulls:
+#   daysUntilStale: 30
+#   markComment: >
+#     This pull request has been automatically marked as stale because it has not had
+#     recent activity. It will be closed if no further activity occurs. Thank you
+#     for your contributions.
+
+# issues:
+#   exemptLabels:
+#     - confirmed

.pre-commit-config.yaml

@@ -11,7 +11,7 @@ ci:
 
 repos:
   - repo: https://github.com/pre-commit/pre-commit-hooks
-    rev: v5.0.0
+    rev: v4.4.0
     hooks:
       - id: check-added-large-files
       - id: check-case-conflict
@@ -25,7 +25,7 @@ repos:
         files: ^(_episodes|code|README.md|setup.md)
 
   - repo: https://github.com/codespell-project/codespell
-    rev: "v2.4.1"
+    rev: "v2.2.2"
     hooks:
       - id: codespell
         args: ["-I", "codespell.txt"]

CONTRIBUTING.md

@@ -22,7 +22,7 @@ agrees to abide by our [code of conduct](CODE_OF_CONDUCT.md).
 The easiest way to get started is to file an issue
 to tell us about a mistake,
 some awkward wording,
-a factual error.
+or a factual error.
 This is a good way to introduce yourself
 and to meet some of our community members.
 
@@ -49,12 +49,12 @@ There are many ways to contribute,
 from writing new exercises and improving existing ones
 to updating or filling in the documentation
 and submitting [bug reports][issues]
-about things that do not work, aren not clear, or are missing.
+about things that do not work, are not clear, or are missing.
 If you are looking for ideas, please see the 'Issues' tab for
 a list of issues associated with this repository,
 or you may also look at all issues in [hsf-training][hsf-training-issues]
 
-There is also [a list][hsf-training-gfis] of all issues that are particularly easy and suitable
+There is also [a list](hsf-training-gfis) of all issues that are particularly easy and suitable
 for first contributions.
 
 Comments on issues and reviews of pull requests are just as welcome: