Merge branch 'main' into release/0.7

.github/workflows/build_documentation.yml

@@ -19,22 +19,15 @@ concurrency:
 
 jobs:
   docs-style:
-    name: Documentation Style Check
+    name: "Check documentation style"
     runs-on: ubuntu-latest
     steps:
-      - uses: actions/checkout@v4
-
-      - name: Running Vale
-        uses: errata-ai/vale-action@reviewdog
-        env:
-          GITHUB_TOKEN: ${{secrets.GITHUB_TOKEN}}
+      - name: "Check documentation style"
+        uses: ansys/actions/doc-style@v4
         with:
-          files: doc
-          reporter: github-pr-check
-          level: error
-          filter_mode: nofilter
-          fail_on_error: true
-          vale_flags: "--config=doc/.vale.ini"
+          token: ${{ secrets.GITHUB_TOKEN }}
+          vale-config: "doc/.vale.ini"
+          vale-version: "2.29.6"
 
   docs_build:
     runs-on: ubuntu-20.04

.github/workflows/unit_tests.yml

@@ -133,7 +133,7 @@ jobs:
         with:
           max_attempts: 3
           retry_on: error
-          timeout_minutes: 40
+          timeout_minutes: 50
           command: |
             testenv\Scripts\Activate.ps1
             Set-Item -Path env:PYTHONMALLOC -Value "malloc"

.pre-commit-config.yaml

@@ -53,7 +53,7 @@ repos:
 
 # validate GitHub workflow files
 - repo: https://github.com/python-jsonschema/check-jsonschema
-  rev: 0.27.0
+  rev: 0.27.1
   hooks:
     - id: check-github-workflows
 

CODE_OF_CONDUCT.md

@@ -0,0 +1,65 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as
+contributors and maintainers pledge to making participation in our
+project and our community a harassment-free experience for everyone,
+regardless of age, body size, 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.
+
+## Our Standards
+
+Examples of behavior that contributes to creating a positive environment
+include:
+
+* Using welcoming and inclusive language
+* Being respectful of differing viewpoints and experiences
+* Gracefully accepting constructive criticism
+* Focusing on what is best for the community
+* Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+* The use of sexualized language or imagery and unwelcome sexual
+  attention or advances
+* Trolling, insulting/derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or electronic
+  address, without explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable
+behavior and are expected to take appropriate and fair corrective action in
+response to any instances of unacceptable behavior.
+
+Project maintainers have the right and responsibility to remove, edit, or reject
+comments, commits, code, wiki edits, issues, and other contributions that are
+not aligned to this Code of Conduct, or to ban temporarily or permanently any
+contributor for other behaviors that they deem inappropriate, threatening,
+offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies both within project spaces and in public spaces
+when an individual is representing the project or its community. Examples of
+representing a project or community include using an official project e-mail
+address, posting via an official social media account, or acting as an appointed
+representative at an online or offline event. Representation of a project may be
+further defined and clarified by project maintainers.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
+version 1.4, available at
+https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
+
+[homepage]: https://www.contributor-covenant.org
+
+For answers to common questions about this code of conduct, see
+https://www.contributor-covenant.org/faq

CONTRIBUTING.md

@@ -0,0 +1,14 @@
+# Contributing
+
+We absolutely welcome any code contributions and we hope that this
+guide will facilitate an understanding of the PyAEDT code
+repository. It is important to note that while the PyAEDT software
+package is maintained by ANSYS and any submissions will be reviewed
+thoroughly before merging, we still seek to foster a community that can
+support user questions and develop new features to make this software
+a useful tool for all users. As such, we welcome and encourage any
+questions or submissions to this repository.
+
+For contributing to this project, please refer to the [PyAnsys Developer's Guide].
+
+[PyAnsys Developer's Guide]: https://dev.docs.pyansys.com/index.html

CONTRIBUTORS.md

@@ -0,0 +1,20 @@
+# Contributors
+
+## Project Lead
+
+* [Massimo Capodiferro](https://github.com/maxcapodi78)
+
+## Individual Contributors
+
+* [Samuel Lopez](https://github.com/Samuelopez-ansys)
+* [Simon Vandenbrouck](https://github.com/svandenb-dev)
+* [Alberto Di Maria](https://github.com/Alberto-DM)
+* [Giulia Malinverno](https://github.com/gmalinve)
+* [Hui Zhou](https://github.com/ring630)
+* [Devin Crawford](https://github.com/dcrawforAtAnsys)
+* [Kathy Pippert](https://github.com/PipKat)
+* [Lorenzo Vecchietti](https://github.com/lorenzovecchietti)
+* [Maxime Rey](https://github.com/MaxJPRey)
+* [Sébastien Morais](https://github.com/SMoraisAnsys)
+* [Matthew Young](https://github.com/myoung301)
+* [Josh Salant](https://github.com/jsalant22)