Merging to master

.github/PULL_REQUEST_TEMPLATE.md

@@ -1,33 +1,39 @@
-<!--- Provide a general summary of your changes in the Title above -->
+<!--- Provide a general summary of your changes in the Title above. -->
+<!--- Do not include backticks (`) in the Title above.  -->
 
 ## Description
 
-<!--- Describe your changes in detail -->
+<!--- Describe your changes in detail. -->
+<!--- Why is this change required? What problem does it solve? -->
+<!--- Do not include backticks (`).  -->
 
-## Motivation and Context
+## Related issue
 
-<!--- Why is this change required? What problem does it solve? -->
-<!--- If it fixes an open issue, please link to the issue here. -->
+<!--- Replace only the '000' with the issue number. -->
+<!--- Do not include a URL. -->
+
+#000
 
 ## How Has This Been Tested?
 
 <!--- Please describe in detail how you tested your changes. -->
-<!--- Include details of your testing environment, the tests you ran to -->
+<!--- Include details of your testing environment, the tests you ran to. -->
 <!--- see how your change affects other areas of the code, etc. -->
+<!--- Do not include backticks (`).  -->
 
 ## Screenshots (if appropriate):
 
 ## Types of changes
 
-<!--- What types of changes does your code introduce? Put an `x` in all the boxes that apply: -->
+<!--- What types of changes does your code introduce? Put an 'x' in all the boxes that apply: -->
 
 - [ ] Bug fix (non-breaking change which fixes an issue)
 - [ ] New feature (non-breaking change which adds functionality)
 - [ ] Breaking change (fix or feature that would cause existing functionality to change)
 
 ## Checklist:
 
-<!--- Go over all the following points, and put an `x` in all the boxes that apply. -->
+<!--- Go over all the following points, and put an 'x' in all the boxes that apply. -->
 <!--- If you're unsure about any of these, don't hesitate to ask. We're here to help! -->
 
 - [ ] My code follows the code style of this project.

.github/workflows/build-time.yml

@@ -3,7 +3,7 @@ name: Build Performance
 on:
   pull_request:
     branches:
-      - master
+      - '*'
 
 jobs:
   build-time:

.github/workflows/codeql-analysis.yml

@@ -2,10 +2,12 @@ name: 'CodeQL'
 
 on:
     push:
-        branches: [ "master" ]
+        branches: 
+          - '*'
     pull_request:
         # The branches below must be a subset of the branches above
-        branches: [" master" ]
+        branches: 
+          - '*'
     schedule:
         - cron: '38 18 * * 4'
 

.github/workflows/docker-image.yml

@@ -2,9 +2,11 @@ name: Docker Image CI
 
 on:
   push:
-    branches: [ "master" ]
+    branches: 
+      - '*'
   pull_request:
-    branches: [ "master" ]
+    branches: 
+     - '*'
 
 jobs:
 

.github/workflows/test.yml

@@ -3,10 +3,10 @@ name: Run Tests
 on:
   push:
     branches:
-      - master
+      - '*'
   pull_request:
     branches:
-      - master
+      - '*'
 
 jobs:
   test:

.github/workflows/validate.yml

@@ -0,0 +1,124 @@
+name: PR Validation
+
+on:
+  pull_request:
+    types: [edited, opened, synchronize, reopened]
+    branches: ["*"]
+
+jobs:
+  validate-pr:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout repository
+        uses: actions/checkout@v2
+
+      - name: Clear all PR labels
+        run: |
+          pr_number=${{ github.event.pull_request.number }}
+          labels=$(curl -s -H "Authorization: token ${{ secrets.GITHUB_TOKEN }}" \
+            "https://api.github.com/repos/${{ github.repository }}/issues/$pr_number/labels" | jq -r '.[].name // empty')
+          for label in $labels; do
+            curl -s -X DELETE -H "Authorization: token ${{ secrets.GITHUB_TOKEN }}" \
+              "https://api.github.com/repos/${{ github.repository }}/issues/$pr_number/labels/$label"
+          done
+
+      - name: Validate PR
+        env:
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+        run: |
+          pr_body="${{ github.event.pull_request.body }}"
+          pr_author="${{ github.event.pull_request.user.login }}"
+          pr_number="${{ github.event.pull_request.number }}"
+          pr_url="${{ github.event.pull_request.html_url }}"
+          repo_full_name="${{ github.repository }}"
+          message="Hello @${pr_author}, your PR is being processed. Here are the results:\n\n"
+          exit_code=0
+
+          echo "Starting PR validation for PR #${pr_number} by ${pr_author}"
+
+          # Function to make GitHub API calls
+          github_api_call() {
+            local method=$1
+            local endpoint=$2
+            local data=$3
+            local url="https://api.github.com/repos/${repo_full_name}/${endpoint}"
+
+            response=$(curl -s -X ${method} -H "Authorization: token ${GITHUB_TOKEN}" -H "Accept: application/vnd.github.v3+json" ${data:+-d "$data"} "$url")
+            echo "API call to ${endpoint}: $response" >&2
+            echo "$response"
+          }
+
+          # Check if PR author is a maintainer
+          permissions=$(github_api_call GET "collaborators/${pr_author}/permission")
+          is_maintainer=$(echo $permissions | jq -r '.permission')
+          echo "Author permissions: $is_maintainer"
+
+          if [[ "$is_maintainer" == "admin" || "$is_maintainer" == "maintain" ]]; then
+            echo "Author is a maintainer, bypassing checks"
+            message+="As a maintainer, your PR is automatically approved and will bypass further checks.\n"
+            github_api_call POST "issues/${pr_number}/labels" '{"labels":["PR:maintainer-bypass"]}'
+          else
+          # echo "Proceeding with checks regardless of maintainer status for testing purposes"
+          # Check PR template
+            if [[ "$pr_body" != *"## Description"* ]] || [[ "$pr_body" != *"## Related issue"* ]]; then
+              exit_code=2
+              echo "PR template not respected. Exit code: $exit_code"
+              reason="PR template is not respected. Please update your PR description to include the required sections."
+              message+="\n- $reason\n\nHere's a minimal example of a valid PR body:\n\n"
+              message+='```markdown\n## Description\n\n[Provide a brief description of your changes]\n\n## Related issue\n\nFixes #123\n```\n'
+              github_api_call POST "issues/${pr_number}/labels" '{"labels":["PR:fix-template"]}'
+            else
+              echo "PR template respected, checking linked issues"
+              # Extract linked issues
+              # issue_numbers=$(echo "$pr_body" | grep -oP '#\K\d+')
+              issue_numbers=$(echo "$pr_body" | grep -o '#[0-9]\+' | cut -d'#' -f2)
+
+              echo "debug linked issues"
+
+              if [ -z "$issue_numbers" ]; then
+                echo "No linked issues detected. Setting default empty value for issue_numbers to avoid error."
+                issue_numbers="empty"
+                exit_code=3
+                echo "No linked issue found. Exit code: $exit_code"
+                reason="No linked issue found. Please link an issue in your PR description (e.g., 'Fixes #123')."
+                message+="\n- $reason"
+                github_api_call POST "issues/${pr_number}/labels" '{"labels":["PR:no-linked-issue"]}'
+              else
+                echo "Linked issues found: $issue_numbers"
+                # Check if PR author is assigned to the linked issue(s)
+                if [[ "$issue_numbers" != "empty" ]]; then
+                  for issue_number in $issue_numbers; do
+                    issue_data=$(github_api_call GET "issues/${issue_number}")
+                    issue_assignees=$(echo "$issue_data" | jq -r '.assignees[].login')
+                    if ! echo "$issue_assignees" | grep -q "$pr_author"; then
+                      exit_code=4
+                      echo "Author not assigned to issue #${issue_number}. Exit code: $exit_code"
+                      reason="PR author is not assigned to the linked issue #$issue_number. Please assign yourself to the issue before submitting a PR."
+                      message+="\n- $reason"
+                      github_api_call POST "issues/${pr_number}/labels" '{"labels":["PR:author-not-assigned"]}'
+                    else
+                      echo "Author is assigned to issue #${issue_number}"
+                    fi
+                  done
+                fi
+              fi
+            fi
+          fi
+
+          # Finalize validation
+          if [ "$exit_code" = 0 ]; then
+            echo "PR is valid"
+            message+="\n\nYour PR is valid and ready for review. Thank you for your contribution!"
+            github_api_call POST "issues/${pr_number}/labels" '{"labels":["PR:ready-for-review"]}'
+          else
+            echo "PR is invalid. Closing PR."
+            message+="\n\nPlease address the above issues and update your PR. Once you've made the necessary changes, the PR will be automatically re-evaluated."
+            github_api_call PATCH "pulls/${pr_number}" '{"state":"closed"}'
+          fi
+
+          # Add comment to PR
+          echo "Adding comment to PR"
+          github_api_call POST "issues/${pr_number}/comments" "{\"body\":\"$message\"}"
+
+          echo "PR validation completed. Exit code: $exit_code"
+          exit $exit_code

CODE_OF_CONDUCT.md

@@ -6,8 +6,8 @@ We as members, contributors, and leaders pledge to make participation in our
 community a harassment-free experience for everyone, regardless of age, body
 size, visible or invisible disability, ethnicity, sex characteristics, gender
 identity and expression, level of experience, education, socio-economic status,
-nationality, personal appearance, race, religion, or sexual identity
-and orientation.
+nationality, personal appearance, race, caste, color, religion, or sexual
+identity and orientation.
 
 We pledge to act and interact in ways that contribute to an open, welcoming,
 diverse, inclusive, and healthy community.
@@ -17,23 +17,23 @@ diverse, inclusive, and healthy community.
 Examples of behavior that contributes to a positive environment for our
 community include:
 
-- Demonstrating empathy and kindness toward other people
-- Being respectful of differing opinions, viewpoints, and experiences
-- Giving and gracefully accepting constructive feedback
-- Accepting responsibility and apologizing to those affected by our mistakes,
+* Demonstrating empathy and kindness toward other people
+* Being respectful of differing opinions, viewpoints, and experiences
+* Giving and gracefully accepting constructive feedback
+* Accepting responsibility and apologizing to those affected by our mistakes,
   and learning from the experience
-- Focusing on what is best not just for us as individuals, but for the
-  overall community
+* Focusing on what is best not just for us as individuals, but for the overall
+  community
 
 Examples of unacceptable behavior include:
 
-- The use of sexualized language or imagery, and sexual attention or
-  advances of any kind
-- Trolling, insulting or derogatory comments, and personal or political attacks
-- Public or private harassment
-- Publishing others' private information, such as a physical or email
-  address, without their explicit permission
-- Other conduct which could reasonably be considered inappropriate in a
+* The use of sexualized language or imagery, and sexual attention or advances of
+  any kind
+* Trolling, insulting or derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or email address,
+  without their explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
   professional setting
 
 ## Enforcement Responsibilities
@@ -52,15 +52,15 @@ decisions when appropriate.
 
 This Code of Conduct applies within all community spaces, and also applies when
 an individual is officially representing the community in public spaces.
-Examples of representing our community include using an official e-mail address,
+Examples of representing our community include using an official email address,
 posting via an official social media account, or acting as an appointed
 representative at an online or offline event.
 
 ## Enforcement
 
 Instances of abusive, harassing, or otherwise unacceptable behavior may be
-reported to the community leaders responsible for enforcement at [email protected]
-.
+reported to the community leaders responsible for enforcement at
+[[email protected]](mailto:[email protected]).
 All complaints will be reviewed and investigated promptly and fairly.
 
 All community leaders are obligated to respect the privacy and security of the
@@ -82,15 +82,15 @@ behavior was inappropriate. A public apology may be requested.
 
 ### 2. Warning
 
-**Community Impact**: A violation through a single incident or series
-of actions.
+**Community Impact**: A violation through a single incident or series of
+actions.
 
 **Consequence**: A warning with consequences for continued behavior. No
 interaction with the people involved, including unsolicited interaction with
 those enforcing the Code of Conduct, for a specified period of time. This
 includes avoiding interactions in community spaces as well as external channels
-like social media. Violating these terms may lead to a temporary or
-permanent ban.
+like social media. Violating these terms may lead to a temporary or permanent
+ban.
 
 ### 3. Temporary Ban
 
@@ -109,20 +109,18 @@ Violating these terms may lead to a permanent ban.
 standards, including sustained inappropriate behavior, harassment of an
 individual, or aggression toward or disparagement of classes of individuals.
 
-**Consequence**: A permanent ban from any sort of public interaction within
-the community.
+**Consequence**: A permanent ban from any sort of public interaction within the
+community.
 
 ## Attribution
 
-This Code of Conduct is adapted from the [Contributor Covenant][homepage],
-version 2.0, available at
-https://www.contributor-covenant.org/version/2/0/code_of_conduct.html.
+This Code of Conduct is adapted from the [Contributor Covenant](https://www.contributor-covenant.org/),
+version 2.1, available at
+https://www.contributor-covenant.org/version/2/1/code_of_conduct.html.
 
-Community Impact Guidelines were inspired by [Mozilla's code of conduct
-enforcement ladder](https://github.com/mozilla/diversity).
-
-[homepage]: https://www.contributor-covenant.org
+Community Impact Guidelines were inspired by
+[Mozilla's code of conduct enforcement ladder](https://github.com/mozilla/inclusion).
 
 For answers to common questions about this code of conduct, see the FAQ at
 https://www.contributor-covenant.org/faq. Translations are available at
-https://www.contributor-covenant.org/translations.
+https://www.contributor-covenant.org/translations.