From 17f2dd864218e47eb0edb783c06792f7d64340a5 Mon Sep 17 00:00:00 2001 From: PyAnsys Automation bot <214123248+pyansys-automation@users.noreply.github.com> Date: Sat, 1 Nov 2025 05:02:16 +0100 Subject: [PATCH 1/5] chore: update CODE_OF_CONDUCT.md file --- CODE_OF_CONDUCT.md | 30 +++++++++++++++--------------- 1 file changed, 15 insertions(+), 15 deletions(-) diff --git a/CODE_OF_CONDUCT.md b/CODE_OF_CONDUCT.md index b4bcbe52..5a9533d3 100644 --- a/CODE_OF_CONDUCT.md +++ b/CODE_OF_CONDUCT.md @@ -1,18 +1,18 @@ -# Contributor Covenant Code of Conduct +# Contributor covenant code of conduct -## Our Pledge +## 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, socioeconomic status, nationality, personal appearance, -race, religion, or sexual identity and orientation. +In the interest of fostering an open and welcoming environment, +all contributors and maintainers pledge to making participation +in the Ansys project and community a harassment-free experience +for everyone, regardless of age, body size, disability, ethnicity, +sex characteristics, gender identity and expression, level of +experience, education, socioeconomic status, nationality, personal +appearance, race, religion, or sexual identity and orientation. -## Our Standards +## Standards -Examples of behavior that contributes to creating a positive environment +Examples of behavior that contribute to creating a positive environment include: * Using welcoming and inclusive language @@ -32,7 +32,7 @@ Examples of unacceptable behavior by participants include: * Other conduct which could reasonably be considered inappropriate in a professional setting -## Our Responsibilities +## Responsibilities Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in @@ -48,14 +48,14 @@ offensive, or harmful. 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 +representing a project or community include using an official project email +address, posting using 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], +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 From 5f074ec9fb0fc42da15d2354dc25eccb1be2382b Mon Sep 17 00:00:00 2001 From: PyAnsys Automation bot <214123248+pyansys-automation@users.noreply.github.com> Date: Sat, 1 Nov 2025 05:02:17 +0100 Subject: [PATCH 2/5] chore: update CONTRIBUTING.md file --- CONTRIBUTING.md | 22 +++++++++------------- 1 file changed, 9 insertions(+), 13 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 71c7c106..5d752a14 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -1,16 +1,12 @@ -# Contributing +# Contribute -We absolutely welcome any code contributions and we hope that this -guide will facilitate an understanding of the ``ansys-tools-path`` code -repository. It is important to note that while the ``ansys-tools-path`` 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. +Overall guidance on contributing to a PyAnsys library appears in the +[Contributing] topic in the *PyAnsys developer's guide*. Ensure that you +are thoroughly familiar with this guide before attempting to contribute to +{project-name}. -For contributing to this project, please refer to the [PyAnsys Developer's Guide]. -Further information about contributing to ``ansys-tools-path`` can be found in [Contributing]. +The following contribution information is specific to {project-name}. -[PyAnsys Developer's Guide]: https://dev.docs.pyansys.com/index.html -[Contributing]: https://path.tools.docs.pyansys.com/dev/contributing.html +[Contributing]: https://dev.docs.pyansys.com/how-to/contributing.html + + From cfc11fae95cee06015138caad09aa4020e27ced7 Mon Sep 17 00:00:00 2001 From: PyAnsys Automation bot <214123248+pyansys-automation@users.noreply.github.com> Date: Sat, 1 Nov 2025 05:02:20 +0100 Subject: [PATCH 3/5] chore: update SECURITY.md file --- SECURITY.md | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) create mode 100644 SECURITY.md diff --git a/SECURITY.md b/SECURITY.md new file mode 100644 index 00000000..5a88c014 --- /dev/null +++ b/SECURITY.md @@ -0,0 +1,16 @@ +# Security Policy + +## Reporting a vulnerability + +> [!CAUTION] +> Do not use GitHub issues to report any security vulnerabilities. + +If you detect a vulnerability, contact the [PyAnsys Core team](mailto:pyansys.core@ansys.com), +mentioning the repository and the details of your finding. The team will address it as soon as possible. + +Provide the PyAnsys Core team with this information: + +- Any specific configuration settings needed to reproduce the problem +- Step-by-step guidance to reproduce the problem +- The exact location of the problematic source code, including tag, branch, commit, or a direct URL +- The potential consequences of the vulnerability, along with a description of how an attacker could take advantage of the issue From b5312616eb378ccd28164c195da69a3282a1093e Mon Sep 17 00:00:00 2001 From: pyansys-ci-bot <92810346+pyansys-ci-bot@users.noreply.github.com> Date: Sat, 1 Nov 2025 04:03:11 +0000 Subject: [PATCH 4/5] chore: adding changelog file 340.maintenance.md [dependabot-skip] --- doc/changelog.d/340.maintenance.md | 1 + 1 file changed, 1 insertion(+) create mode 100644 doc/changelog.d/340.maintenance.md diff --git a/doc/changelog.d/340.maintenance.md b/doc/changelog.d/340.maintenance.md new file mode 100644 index 00000000..cc5bbf76 --- /dev/null +++ b/doc/changelog.d/340.maintenance.md @@ -0,0 +1 @@ +Update missing or outdated files From e481aae291194fb3dabe800851cb54f917487e50 Mon Sep 17 00:00:00 2001 From: Roberto Pastor Muela <37798125+RobPasMue@users.noreply.github.com> Date: Mon, 3 Nov 2025 07:56:41 +0100 Subject: [PATCH 5/5] Update CONTRIBUTING.md --- CONTRIBUTING.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 5d752a14..64ee5495 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -3,7 +3,7 @@ Overall guidance on contributing to a PyAnsys library appears in the [Contributing] topic in the *PyAnsys developer's guide*. Ensure that you are thoroughly familiar with this guide before attempting to contribute to -{project-name}. +ansys-tools-path. The following contribution information is specific to {project-name}.