From 8635fd210bbd88f2b5a73a67236a41300c8eeccb Mon Sep 17 00:00:00 2001 From: Pranav M S Krishnan Date: Tue, 26 May 2026 16:36:58 +0530 Subject: [PATCH 1/4] Add Contributor Covenant Code of Conduct This document outlines the Contributor Covenant Code of Conduct, detailing the community's pledge, standards, enforcement responsibilities, and consequences for violations. Signed-off-by: Pranav M S Krishnan --- CODE_OF_CONDUCT.md | 128 +++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 128 insertions(+) create mode 100644 CODE_OF_CONDUCT.md diff --git a/CODE_OF_CONDUCT.md b/CODE_OF_CONDUCT.md new file mode 100644 index 0000000..805f784 --- /dev/null +++ b/CODE_OF_CONDUCT.md @@ -0,0 +1,128 @@ +# Contributor Covenant Code of Conduct + +## Our Pledge + +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. + +We pledge to act and interact in ways that contribute to an open, welcoming, +diverse, inclusive, and healthy community. + +## Our Standards + +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, + and learning from the experience +* 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 + professional setting + +## Enforcement Responsibilities + +Community leaders are responsible for clarifying and enforcing our standards of +acceptable behavior and will take appropriate and fair corrective action in +response to any behavior that they deem inappropriate, threatening, offensive, +or harmful. + +Community leaders 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, and will communicate reasons for moderation +decisions when appropriate. + +## Scope + +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, +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 +pycontributors@gmail.com. +All complaints will be reviewed and investigated promptly and fairly. + +All community leaders are obligated to respect the privacy and security of the +reporter of any incident. + +## Enforcement Guidelines + +Community leaders will follow these Community Impact Guidelines in determining +the consequences for any action they deem in violation of this Code of Conduct: + +### 1. Correction + +**Community Impact**: Use of inappropriate language or other behavior deemed +unprofessional or unwelcome in the community. + +**Consequence**: A private, written warning from community leaders, providing +clarity around the nature of the violation and an explanation of why the +behavior was inappropriate. A public apology may be requested. + +### 2. Warning + +**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. + +### 3. Temporary Ban + +**Community Impact**: A serious violation of community standards, including +sustained inappropriate behavior. + +**Consequence**: A temporary ban from any sort of interaction or public +communication with the community for a specified period of time. No public or +private interaction with the people involved, including unsolicited interaction +with those enforcing the Code of Conduct, is allowed during this period. +Violating these terms may lead to a permanent ban. + +### 4. Permanent Ban + +**Community Impact**: Demonstrating a pattern of violation of community +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. + +## 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. + +Community Impact Guidelines were inspired by [Mozilla's code of conduct +enforcement ladder](https://github.com/mozilla/diversity). + +[homepage]: https://www.contributor-covenant.org + +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. From c1f91d80a15dc2cd29c12fc4d40274083ff4d417 Mon Sep 17 00:00:00 2001 From: Pranav M S Krishnan Date: Tue, 26 May 2026 17:41:01 +0530 Subject: [PATCH 2/4] Add welcome workflow for first-time contributors This workflow welcomes first-time issue and PR authors with personalized messages. Signed-off-by: Pranav M S Krishnan --- .github/workflows/welcome.yml | 44 +++++++++++++++++++++++++++++++++++ 1 file changed, 44 insertions(+) create mode 100644 .github/workflows/welcome.yml diff --git a/.github/workflows/welcome.yml b/.github/workflows/welcome.yml new file mode 100644 index 0000000..1ad896a --- /dev/null +++ b/.github/workflows/welcome.yml @@ -0,0 +1,44 @@ +name: Welcome Bot + +on: + issues: + types: [opened] + pull_request_target: + types: [opened] + +jobs: + welcome: + runs-on: ubuntu-latest + permissions: + issues: write + pull-requests: write + + steps: + - name: Welcome First-Time Issue Author + if: github.event_name == 'issues' + uses: actions/first-interaction@v1 + with: + repo-token: ${{ secrets.GITHUB_TOKEN }} + issue-message: | + 👋 Welcome to the chaos, @${{ github.event.issue.user.login }}! + + Thanks for opening your first issue on **is-one-one**. Our team (of tired + engineering students) will look into this soon! 🎉 + + While you wait, feel free to browse our [Methods Directory](https://github.com/Py-Contributors/is-one-one/blob/main/docs/METHODS.md) + and marvel at all the unnecessary ways we've already proven that `1 == 1`. + + - name: Welcome First-Time PR Author + if: github.event_name == 'pull_request_target' + uses: actions/first-interaction@v1 + with: + repo-token: ${{ secrets.GITHUB_TOKEN }} + pr-message: | + 👋 Welcome to the chaos, @${{ github.event.pull_request.user.login }}! + + Thanks for opening your first PR on **is-one-one**. Our team (of tired + engineering students) will look into this soon! 🎉 + + Our CI bot will now run the **Automated Logic Suite** to confirm that your + contribution hasn't accidentally caused `1 != 1`. Sit tight — mathematics + is being verified as we speak. 🧠 From 6bccb622c36ad9f9b13573b3b59a0c0461df5101 Mon Sep 17 00:00:00 2001 From: Pranav M S Krishnan Date: Tue, 26 May 2026 19:06:57 +0530 Subject: [PATCH 3/4] Enhance welcome messages for first-time contributors Updated welcome messages for issues and pull requests to be more engaging and informative. Signed-off-by: Pranav M S Krishnan --- .github/workflows/welcome.yml | 20 ++++++++------------ 1 file changed, 8 insertions(+), 12 deletions(-) diff --git a/.github/workflows/welcome.yml b/.github/workflows/welcome.yml index 1ad896a..633706a 100644 --- a/.github/workflows/welcome.yml +++ b/.github/workflows/welcome.yml @@ -5,7 +5,8 @@ on: types: [opened] pull_request_target: types: [opened] - + workflow_dispatch: # Allows the maintainer to run this workflow manually + jobs: welcome: runs-on: ubuntu-latest @@ -20,13 +21,11 @@ jobs: with: repo-token: ${{ secrets.GITHUB_TOKEN }} issue-message: | - 👋 Welcome to the chaos, @${{ github.event.issue.user.login }}! + 👋 Welcome to **is-one-one**, @${{ github.event.issue.user.login }}! - Thanks for opening your first issue on **is-one-one**. Our team (of tired - engineering students) will look into this soon! 🎉 + Thanks for opening your first issue. Our team of engineering students will look into this soon! We love exploring new and creative ways to prove `1 == 1`. - While you wait, feel free to browse our [Methods Directory](https://github.com/Py-Contributors/is-one-one/blob/main/docs/METHODS.md) - and marvel at all the unnecessary ways we've already proven that `1 == 1`. + While you wait, please take a look at our [Contributing Guidelines](https://github.com) to see how we structure our project. We look forward to collaborating with you! 🚀 - name: Welcome First-Time PR Author if: github.event_name == 'pull_request_target' @@ -34,11 +33,8 @@ jobs: with: repo-token: ${{ secrets.GITHUB_TOKEN }} pr-message: | - 👋 Welcome to the chaos, @${{ github.event.pull_request.user.login }}! + 👋 Welcome to **is-one-one**, @${{ github.event.pull_request.user.login }}! - Thanks for opening your first PR on **is-one-one**. Our team (of tired - engineering students) will look into this soon! 🎉 + Thank you for submitting your first pull request! We really appreciate your time and effort in contributing to the project. - Our CI bot will now run the **Automated Logic Suite** to confirm that your - contribution hasn't accidentally caused `1 != 1`. Sit tight — mathematics - is being verified as we speak. 🧠 + Our automated test suite will run shortly to verify your contribution. In the meantime, please review our [Contributing Guidelines](https://github.com) to ensure your PR matches our repository requirements. Happy coding! 🧠 From f44f26082b9ee79b1a4e5bc156835413689d587e Mon Sep 17 00:00:00 2001 From: Pranav M S Krishnan Date: Wed, 27 May 2026 12:25:20 +0530 Subject: [PATCH 4/4] Fix links to Contributing Guidelines in welcome.yml Updated links to the Contributing Guidelines in welcome messages for issues and pull requests. Signed-off-by: Pranav M S Krishnan --- .github/workflows/welcome.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/.github/workflows/welcome.yml b/.github/workflows/welcome.yml index 633706a..bcbbbd2 100644 --- a/.github/workflows/welcome.yml +++ b/.github/workflows/welcome.yml @@ -25,7 +25,7 @@ jobs: Thanks for opening your first issue. Our team of engineering students will look into this soon! We love exploring new and creative ways to prove `1 == 1`. - While you wait, please take a look at our [Contributing Guidelines](https://github.com) to see how we structure our project. We look forward to collaborating with you! 🚀 + While you wait, please take a look at our [Contributing Guidelines](https://github.com/Py-Contributors/is-one-one/blob/85c9377cad3dd45a38b117f53dbbef99158c0224/CONTRIBUTING.md) to see how we structure our project. We look forward to collaborating with you! 🚀 - name: Welcome First-Time PR Author if: github.event_name == 'pull_request_target' @@ -37,4 +37,4 @@ jobs: Thank you for submitting your first pull request! We really appreciate your time and effort in contributing to the project. - Our automated test suite will run shortly to verify your contribution. In the meantime, please review our [Contributing Guidelines](https://github.com) to ensure your PR matches our repository requirements. Happy coding! 🧠 + Our automated test suite will run shortly to verify your contribution. In the meantime, please review our [Contributing Guidelines](https://github.com/Py-Contributors/is-one-one/blob/85c9377cad3dd45a38b117f53dbbef99158c0224/CONTRIBUTING.md) to ensure your PR matches our repository requirements. Happy coding! ðŸ§