🤖 Sync org-wide files to upstream repo (JuliaLang#414)

More info: exercism/org-wide-files@53f1670

.github/labels.yml

@@ -1,31 +1,25 @@
-# ------------------------------------------------------------- #
-# This is an auto-generated file - Do not edit it file directly #
-# ------------------------------------------------------------- #
+# --------------------------------------------------------------- #
+# This is an auto-generated file - Do not manually edit this file #
+# --------------------------------------------------------------- #
 
-# This file is automatically generated by merging two files:
-# 1. The Exercism-wide labels
-# 2. The repository-specific labels
+# This file is automatically generated by concatenating two files:
 #
-# The Exercism-wide labels are defined in
-# https://github.com/exercism/org-wide-files/blob/main/synced-files/.github/labels.yml
+# 1. The Exercism-wide labels: defined in https://github.com/exercism/org-wide-files/blob/main/global-files/.github/labels.yml
+# 2. The repository-specific labels: defined in the `.appends/.github/labels.yml` file within this repository.
 #
-# The repository-specific labels are defined in `.appends/.github/labels.yml`.
-# If you want to change the repository-specific labels, update the
-# `.appends/.github/labels.yml` file and _not_ this file.
+# If any of these two files change, a pull request is automatically containing a re-generated version of this file.
+# Consequently, to change repository-specific labels you should update the `.appends/.github/labels.yml` file and _not_ this file.
 #
-# Any changes to the repo's `.appends/.github/labels.yml` file or the
-# Exercism-wide `labels.yml` file will automatically result in this file being
-# regenerated and the labels being updated. This typically takes 5-10 minutes.
+# When the pull request has been merged, the GitHub labels will be automatically updated by the "Sync labels" workflow.
+# This typically takes 5-10 minutes.
 
 # --------------------------------------------------------------------- #
 # These are the Exercism-wide labels which are shared across all repos. #
 # --------------------------------------------------------------------- #
 
-# The following Exercism-wide labels are used to show "tasks" on the website, which
-# will point users to things they can help contribute with.
+# The following Exercism-wide labels are used to show "tasks" on the website, which will point users to things they can help contribute with.
 
-# The `x:action/<value>` labels describe what sort of work the contributor
-# will be engaged in when working on the issue
+# 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"
@@ -46,8 +40,7 @@
   description: "Sync content with its latest version"
   color: "6f60d2"
 
-# The `x:knowledge/<value>` labels describe how much Exercism knowledge
-# is required by the contributor
+# 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"
@@ -64,8 +57,7 @@
   description: "Comprehensive Exercism knowledge required"
   color: "604fcd"
 
-# The `x:module/<value>` labels indicate what part of Exercism
-# the contributor will be working on
+# 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"
@@ -94,8 +86,7 @@
   description: "Work on Test Runners"
   color: "5240c9"
 
-# The `x:size/<value>` labels describe the expected amount of work
-# for a contributor
+# 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"
@@ -116,20 +107,18 @@
   description: "Massive amount of work"
   color: "4836bf"
 
-# The `x:status/<value>` label indicates if there is already someone
-# working on the issue
+# 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"
 
-# The `x:type/<value>` labels describe how much Exercism knowledge
-# is required by the contributor
+# 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"
 
 - name: "x:type/coding"
-  description: "Work on code that will run in production"
+  description: "Write code that is not student-facing content (e.g. test-runners, generators, but not exercises)"
   color: "3c2d9f"
 
 - name: "x:type/content"
@@ -144,20 +133,7 @@
   description: "Work on Documentation"
   color: "3c2d9f"
 
-# The following Exercism-wide labels are used to influence how much reputation
-# a contributor gets for an authored/merged/reviewed PR.
-# See https://github.com/exercism/docs/blob/main/product/reputation.md
-
-- name: "reputation/contributed_code/major"
-  description: "Increases the number of reputation points awarded by this PR"
-  color: "fcfa9f"
-
-- name: "reputation/contributed_code/minor"
-  description: "Decreases the number of reputation points awarded by this PR"
-  color: "fcfa9f"
-
-# This Exercism-wide label is added to all automatically created pull requests
-# that help migrate/prepare a track for Exercism v3
+# This Exercism-wide label is added to all automatically created pull requests that help migrate/prepare a track for Exercism v3
 - name: "v3-migration 🤖"
   description: "Preparing for Exercism v3"
   color: "e99695"

CODE_OF_CONDUCT.md

@@ -13,3 +13,11 @@ While "Julia" is a female name in many parts of the world, the programming langu
 
 In natural languages where attaching a grammatical gender to the name "Julia" is unavoidable, exceptions may be made.
 However, consider using language constructs such as "the programming language Julia" and then referring to "the programming language" whenever possible.
+
+## Addendum
+
+Furthermore, on the Julia-specific repos and website sections, do not sexualize or genderize the term "Julia" or any other aspects of the project.
+While "Julia" is a female name in many parts of the world, the programming language is not a person and does not have a gender.
+
+In natural languages where attaching a grammatical gender to the name "Julia" is unavoidable, exceptions may be made.
+However, consider using language constructs such as "the programming language Julia" and then referring to "the programming language" whenever possible.