Merge branch 'main' into bird-watcher

Author: andrerfcsantos

.appends/.github/labels.yml

@@ -3,14 +3,6 @@
 # https://github.com/exercism/org-wide-files/blob/main/global-files/.github/labels.yml.     #
 # ----------------------------------------------------------------------------------------- #
 
-- name: "README/discrepancy"
-  description: ""
-  color: "d93f0b"
-
-- name: "README/inadequate"
-  description: ""
-  color: "d93f0b"
-
 - name: "action/stale"
   description: "Applied (and removed) automatically by the stale workflow to indicate an issue or pull request is stale"
   color: "d93f0b"
@@ -23,12 +15,8 @@
   description: "This pull request is waiting on the contributor."
   color: "4231af"
 
-- name: "status/future"
-  description: "This pull request needs to be reconsidered at some point in the future."
-  color: "4231af"
-
 - name: "bug"
-  description: ""
+  description: "Marks that something is broken and needs to be fixed."
   color: "fc2929"
 
 - name: "dependencies"
@@ -47,18 +35,10 @@
   description: ""
   color: "7057ff"
 
-- name: "hacktoberfest"
-  description: ""
-  color: "cc8744"
-
 - name: "help wanted"
   description: ""
   color: "5319e7"
 
-- name: "in-progress"
-  description: ""
-  color: "9FDB12"
-
 - name: "invalid"
   description: ""
   color: "e6e6e6"
@@ -72,7 +52,11 @@
   color: "0052cc"
 
 - name: "pinned"
-  description: ""
+  description: "Shown at the top of the issue page"
+  color: "fef2c0"
+
+- name: "discussion"
+  description: "This is a topic for a longer discussion. The issue can stay open for a while."
   color: "fef2c0"
 
 - name: "problem-spec"
@@ -83,18 +67,14 @@
   description: ""
   color: "cc317c"
 
-- name: "test suite"
-  description: ""
-  color: "f9d0c4"
-
-- name: "v3"
-  description: ""
-  color: "13B0D1"
-
 - name: "wontfix"
   description: ""
   color: "ffffff"
 
-- name: "september-sprint"
-  description: "Part of the September sprint to get the Go track in great shape"
-  color: "0846af"
+- name: "abandoned"
+  description: "The creator of this issue or PR does not respond anymore."
+  color: "c7c5c5"
+
+- name: "chore"
+  description: "Some cleanup/house-keeping needs to be done here."
+  color: "495747"

.github/labels.yml

@@ -22,116 +22,116 @@
 # The `x:action/<value>` labels describe what sort of work the contributor will be engaged in when working on the issue
 - name: "x:action/create"
   description: "Work on something from scratch"
-  color: "6f60d2"
+  color: "ffffff"
 
 - name: "x:action/fix"
   description: "Fix an issue"
-  color: "6f60d2"
+  color: "ffffff"
 
 - name: "x:action/improve"
   description: "Improve existing functionality/content"
-  color: "6f60d2"
+  color: "ffffff"
 
 - name: "x:action/proofread"
   description: "Proofread text"
-  color: "6f60d2"
+  color: "ffffff"
 
 - name: "x:action/sync"
   description: "Sync content with its latest version"
-  color: "6f60d2"
+  color: "ffffff"
 
 # The `x:knowledge/<value>` labels describe how much Exercism knowledge is required by the contributor
 - name: "x:knowledge/none"
   description: "No existing Exercism knowledge required"
-  color: "604fcd"
+  color: "ffffff"
 
 - name: "x:knowledge/elementary"
   description: "Little Exercism knowledge required"
-  color: "604fcd"
+  color: "ffffff"
 
 - name: "x:knowledge/intermediate"
   description: "Quite a bit of Exercism knowledge required"
-  color: "604fcd"
+  color: "ffffff"
 
 - name: "x:knowledge/advanced"
   description: "Comprehensive Exercism knowledge required"
-  color: "604fcd"
+  color: "ffffff"
 
 # The `x:module/<value>` labels indicate what part of Exercism the contributor will be working on
 - name: "x:module/analyzer"
   description: "Work on Analyzers"
-  color: "5240c9"
+  color: "ffffff"
 
 - name: "x:module/concept"
   description: "Work on Concepts"
-  color: "5240c9"
+  color: "ffffff"
 
 - name: "x:module/concept-exercise"
   description: "Work on Concept Exercises"
-  color: "5240c9"
+  color: "ffffff"
 
 - name: "x:module/generator"
   description: "Work on Exercise generators"
-  color: "5240c9"
+  color: "ffffff"
 
 - name: "x:module/practice-exercise"
   description: "Work on Practice Exercises"
-  color: "5240c9"
+  color: "ffffff"
 
 - name: "x:module/representer"
   description: "Work on Representers"
-  color: "5240c9"
+  color: "ffffff"
 
 - name: "x:module/test-runner"
   description: "Work on Test Runners"
-  color: "5240c9"
+  color: "ffffff"
 
 # The `x:size/<value>` labels describe the expected amount of work for a contributor
 - name: "x:size/tiny"
   description: "Tiny amount of work"
-  color: "4836bf"
+  color: "ffffff"
 
 - name: "x:size/small"
   description: "Small amount of work"
-  color: "4836bf"
+  color: "ffffff"
 
 - name: "x:size/medium"
   description: "Medium amount of work"
-  color: "4836bf"
+  color: "ffffff"
 
 - name: "x:size/large"
   description: "Large amount of work"
-  color: "4836bf"
+  color: "ffffff"
 
 - name: "x:size/massive"
   description: "Massive amount of work"
-  color: "4836bf"
+  color: "ffffff"
 
 # The `x:status/<value>` label indicates if there is already someone working on the issue
 - name: "x:status/claimed"
   description: "Someone is working on this issue"
-  color: "4231af"
+  color: "ffffff"
 
 # The `x:type/<value>` labels describe what type of work the contributor will be engaged in
 - name: "x:type/ci"
   description: "Work on Continuous Integration (e.g. GitHub Actions workflows)"
-  color: "3c2d9f"
+  color: "ffffff"
 
 - name: "x:type/coding"
   description: "Write code that is not student-facing content (e.g. test-runners, generators, but not exercises)"
-  color: "3c2d9f"
+  color: "ffffff"
 
 - name: "x:type/content"
   description: "Work on content (e.g. exercises, concepts)"
-  color: "3c2d9f"
+  color: "ffffff"
 
 - name: "x:type/docker"
   description: "Work on Dockerfiles"
-  color: "3c2d9f"
+  color: "ffffff"
 
 - name: "x:type/docs"
   description: "Work on Documentation"
-  color: "3c2d9f"
+  color: "ffffff"
 
 # This label can be added to accept PRs as part of Hacktoberfest
 - name: "hacktoberfest-accepted"
@@ -148,14 +148,6 @@
 # https://github.com/exercism/org-wide-files/blob/main/global-files/.github/labels.yml.     #
 # ----------------------------------------------------------------------------------------- #
 
-- name: "README/discrepancy"
-  description: ""
-  color: "d93f0b"
-
-- name: "README/inadequate"
-  description: ""
-  color: "d93f0b"
-
 - name: "action/stale"
   description: "Applied (and removed) automatically by the stale workflow to indicate an issue or pull request is stale"
   color: "d93f0b"
@@ -168,12 +160,8 @@
   description: "This pull request is waiting on the contributor."
   color: "4231af"
 
-- name: "status/future"
-  description: "This pull request needs to be reconsidered at some point in the future."
-  color: "4231af"
-
 - name: "bug"
-  description: ""
+  description: "Marks that something is broken and needs to be fixed."
   color: "fc2929"
 
 - name: "dependencies"
@@ -192,18 +180,10 @@
   description: ""
   color: "7057ff"
 
-- name: "hacktoberfest"
-  description: ""
-  color: "cc8744"
-
 - name: "help wanted"
   description: ""
   color: "5319e7"
 
-- name: "in-progress"
-  description: ""
-  color: "9FDB12"
-
 - name: "invalid"
   description: ""
   color: "e6e6e6"
@@ -217,7 +197,11 @@
   color: "0052cc"
 
 - name: "pinned"
-  description: ""
+  description: "Shown at the top of the issue page"
+  color: "fef2c0"
+
+- name: "discussion"
+  description: "This is a topic for a longer discussion. The issue can stay open for a while."
   color: "fef2c0"
 
 - name: "problem-spec"
@@ -228,18 +212,14 @@
   description: ""
   color: "cc317c"
 
-- name: "test suite"
-  description: ""
-  color: "f9d0c4"
-
-- name: "v3"
-  description: ""
-  color: "13B0D1"
-
 - name: "wontfix"
   description: ""
   color: "ffffff"
 
-- name: "september-sprint"
-  description: "Part of the September sprint to get the Go track in great shape"
-  color: "0846af"
+- name: "abandoned"
+  description: "The creator of this issue or PR does not respond anymore."
+  color: "c7c5c5"
+
+- name: "chore"
+  description: "Some cleanup/house-keeping needs to be done here."
+  color: "495747"

.github/pr-commenter.yml

@@ -0,0 +1,68 @@
+comment:
+  on-update: edit
+  glob-options:
+    dot: true
+
+  header: |
+    ### Dear {{ prAuthor }}
+    Thank you for contributing to the Go track on Exercism! 💙
+    You will see some automated feedback below 🤖. It would be great if you can make sure your PR covers those points. This will save your reviewer some time and your change can be merged quicker.
+
+  footer: |
+
+    <sub>Automated comment created by [PR Commenter](https://github.com/exercism/pr-commenter-action) 🤖.</sub>
+
+  snippets:
+    - id: concept-changes
+      files:
+        - 'exercises/concept/*/.docs/introduction.md'
+        - 'concepts/*/introduction.md'
+        - 'concepts/*/about.md'
+      body: |
+        - 📜 The following files usually contain very similar content.
+          - `concepts/<concept>/about.md`
+          - `concepts/<concept>/introduction.md`
+          - `exercises/concept/<exercise>/.docs/introduction.md`
+
+          Please check whether the changes you made to one of these also need to be applied to the others.
+
+    - id: exemplar-or-stub-changes
+      files:
+        - 'exercises/concept/*/.meta/*.go'
+        - any:
+            - 'exercises/concept/*/*.go'
+            - '!exercises/concept/*/*_test.go'
+      body: |
+        - 🧦 If you changed the function signature or the function comment in the exemplar file or the sub file (`<exercise>.go`), make sure the change is applied to both files.
+
+    - id: problem-spec-related
+      files:
+        - 'exercises/practice/*/*_test.go'
+        - 'exercises/practice/*/.docs/instructions.md'
+      body: |
+        - ⬆️ The instructions and test cases for many practice exercises originate in the Exercism-wide [problem-specifications repo](https://github.com/exercism/problem-specifications). If the exercise you changed is listed there in the [exercises folder](https://github.com/exercism/problem-specifications/tree/main/exercises), please consider the following.
+          - Improvements to the `instructions.md` file should be made in the problem-spec repo so that all tracks can benefit.
+            You can open a PR there instead.
+          - If you want to add some language specific information, use the `instructions.append.md` file (see [Practice Exercise Docs](https://exercism.org/docs/building/tracks/practice-exercises)).
+          - Test cases selected in the `.meta/tests.toml` file need to be implemented in the `<exercise>_test.go` file according to the specification in [`canonical-data.json`](https://github.com/exercism/problem-specifications#test-data-canonical-datajson).
+
+    - id: note-for-contributors
+      files:
+        - '*'
+        - '**/*'
+      body: |
+        - ✍️ If your PR is not related to an existing issue (and is not self-explaining like a typo fix), please make sure the description explains why the change you made is necessary.
+
+        - 🔤 If your PR fixes an easy to identify typo, if would be great if you could check for that typo in the whole repo. For example, if you found `Unicdoe`, use "replace all" in your editor (or command line magic) to fix it consistently.
+
+    - id: note-for-maintainers
+      files:
+        - '*'
+        - '**/*'
+      body: |
+        ### Dear Reviewer/Maintainer
+        - 📏 Make sure you set the appropriate **`x:size` label** for the PR. (This also works after merging, in case you forgot about it.)
+
+        - 🔍 **Don't be too nit-picky.** If the PR is a clear improvement compared to the status quo, it should be approved as clear signal this is good to be merged even if the minor comments you might have are not addressed by the contributor. Further improvement ideas can be captured in issues (if important enough) and implemented via additional PRs.
+
+        - 🤔 After reviewing the diff in the "Files changed" section, take a moment to think about whether there are **changes missing** from the diff. Does something need to be adjusted in other places so the code or content stays consistent?