From 52de1ce35afe512af61782b38f9fc310ee4392a9 Mon Sep 17 00:00:00 2001 From: Jemimah Date: Tue, 25 Aug 2026 04:13:47 +0100 Subject: [PATCH 1/8] Revise Code of Conduct for clarity and inclusivity Updated the Contributor Covenant Code of Conduct to enhance clarity and ensure a harassment-free environment for all community members. Adjusted language for better readability and understanding. --- CODE_OF_CONDUCT.md | 107 ++++++++++++++++++++++++++++++++++----------- 1 file changed, 82 insertions(+), 25 deletions(-) diff --git a/CODE_OF_CONDUCT.md b/CODE_OF_CONDUCT.md index 6fd21d1..8856058 100644 --- a/CODE_OF_CONDUCT.md +++ b/CODE_OF_CONDUCT.md @@ -2,79 +2,136 @@ ## Our Pledge -We as members, contributors, and leaders pledge to make participation in the **AutoPilot** 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, caste, color, religion, or sexual identity and orientation. +We as members, contributors, and leaders pledge to make participation in the +**AutoPilot** 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, +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. +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: +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 +* 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 +* 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 electronic address, without their explicit permission -* Other conduct which could reasonably be considered inappropriate in a professional setting +* Publishing others' private information, such as a physical or electronic + 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 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. +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 email address, posting via an official social media account, or acting as an appointed representative at an online or offline event. +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 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 by opening a private issue or contacting the maintainers directly via GitHub. All complaints will be reviewed and investigated promptly and fairly. +Instances of abusive, harassing, or otherwise unacceptable behavior may be +reported to the community leaders responsible for enforcement via a direct +message to a maintainer on GitHub. Please do not report Code of Conduct +violations in public issues or discussions โ€” reports should go through a +private channel so the situation can be reviewed fairly and confidentially. -All community leaders are obligated to respect the privacy and security of the reporter of any incident. +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. + +> **Note:** This channel is for conduct issues only. If you've found a +> security vulnerability (e.g. involving Stellar keypairs, vault encryption, +> or fund custody), do **not** report it here or in a public issue โ€” follow +> the responsible disclosure process in [SECURITY.md](./SECURITY.md) instead. ## 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: +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. +**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. +**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. +**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. +**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. +**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. +**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. +**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. +**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.1, available at [https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1]. +This Code of Conduct is adapted from the [Contributor Covenant][homepage], +version 2.1, available at +[https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1]. -Community Impact Guidelines were inspired by [Mozilla's code of conduct enforcement ladder][Mozilla CoC]. +Community Impact Guidelines were inspired by +[Mozilla's code of conduct enforcement ladder][Mozilla CoC]. -For answers to common questions about this code of conduct, see the FAQ at [https://www.contributor-covenant.org/faq][FAQ]. Translations are available at [https://www.contributor-covenant.org/translations][translations]. +For answers to common questions about this code of conduct, see the FAQ at +[https://www.contributor-covenant.org/faq][FAQ]. Translations are available at +[https://www.contributor-covenant.org/translations][translations]. [homepage]: https://www.contributor-covenant.org [v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html From e715a6c24a29fe8ff4f157eff0dc9ea210902dba Mon Sep 17 00:00:00 2001 From: Jemimah Date: Tue, 25 Aug 2026 04:20:36 +0100 Subject: [PATCH 2/8] Add LICENSE file --- LICENSE | 3 +++ 1 file changed, 3 insertions(+) diff --git a/LICENSE b/LICENSE index e1ae602..76fa7ab 100644 --- a/LICENSE +++ b/LICENSE @@ -19,3 +19,6 @@ AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. + +For the full text of this license, see: +https://opensource.org/license/mit/ From 8d8baf8ffdcc13bbc53fe971cdc97aa1cfa67ea2 Mon Sep 17 00:00:00 2001 From: Jemimah Date: Tue, 25 Aug 2026 04:42:32 +0100 Subject: [PATCH 3/8] Add Rust/Soroban CLI version field to bug report Added a new field for Rust/Soroban CLI version in the bug report template. --- .github/ISSUE_TEMPLATE/bug_report.md | 1 + 1 file changed, 1 insertion(+) diff --git a/.github/ISSUE_TEMPLATE/bug_report.md b/.github/ISSUE_TEMPLATE/bug_report.md index a23e3cc..7df8178 100644 --- a/.github/ISSUE_TEMPLATE/bug_report.md +++ b/.github/ISSUE_TEMPLATE/bug_report.md @@ -35,6 +35,7 @@ assignees: "" | Stellar Network | โ˜ Testnet โ˜ Mainnet | | Freighter Wallet version | e.g. 5.8.0 | | AutoPilot version / commit | e.g. `a8ea9ff` | +| Rust / Soroban CLI version (if contract-related) | e.g. `rustc 1.79.0`, `stellar-cli 21.0.0` | ## ๐Ÿ“‹ Logs / Error Output From d48b9d7c73d89b56060e9e7d1a148ac36d98c497 Mon Sep 17 00:00:00 2001 From: Jemimah Date: Tue, 25 Aug 2026 04:48:23 +0100 Subject: [PATCH 4/8] Delete .github/pull_request_template.md --- .github/pull_request_template.md | 67 -------------------------------- 1 file changed, 67 deletions(-) delete mode 100644 .github/pull_request_template.md diff --git a/.github/pull_request_template.md b/.github/pull_request_template.md deleted file mode 100644 index 4165ef4..0000000 --- a/.github/pull_request_template.md +++ /dev/null @@ -1,67 +0,0 @@ -## ๐Ÿ”— Related Issue(s) - - - -Closes # - ---- - -## ๐Ÿ“ Description - - - -## ๐Ÿ—๏ธ Type of Change - - -- [ ] ๐Ÿ› Bug fix (non-breaking change that fixes an issue) -- [ ] โœจ New feature (non-breaking change that adds functionality) -- [ ] ๐Ÿ’ฅ Breaking change (fix or feature that would cause existing functionality to change) -- [ ] ๐Ÿ“œ Smart contract change (Soroban / Rust) -- [ ] ๐ŸŒ Stellar network integration change -- [ ] ๐Ÿ“š Documentation update -- [ ] ๐Ÿ”ง Refactor / code cleanup -- [ ] ๐Ÿงช Test only - -## ๐Ÿงช How Has This Been Tested? - - - -- [ ] Unit tests -- [ ] Integration tests -- [ ] Manual testing on Stellar Testnet -- [ ] Contract simulation (`stellar contract invoke --simulate-only`) - -**Test configuration:** -- Node.js version: -- Network: Testnet / Mainnet -- Relevant wallet address (testnet only): - -## ๐Ÿ“ธ Screenshots / Recordings - - - -## โœ… Checklist - -- [ ] My code follows the project's code style (ESLint + Prettier / Rustfmt) -- [ ] I have performed a self-review of my own code -- [ ] I have commented my code where necessary, particularly in hard-to-understand areas -- [ ] I have made corresponding changes to the documentation -- [ ] My changes generate no new warnings in CI -- [ ] I have added tests that prove my fix is effective or that my feature works -- [ ] All existing tests pass locally -- [ ] For contract changes: I have run `cargo test` and `stellar contract build` -- [ ] I have checked that no secrets or private keys are exposed in this PR - -## ๐Ÿ” Security Considerations - - - -## ๐Ÿ“ฆ Deployment Notes - - - -## ๐Ÿ”— Additional Context - - From 5583626136b20846498d57a360b4ba5c0b5f1007 Mon Sep 17 00:00:00 2001 From: Jemimah Date: Tue, 25 Aug 2026 04:49:25 +0100 Subject: [PATCH 5/8] Create pull request template for contributions Added a pull request template to standardize PR submissions. --- .../ISSUE_TEMPLATE/pull_request_template.md | 68 +++++++++++++++++++ 1 file changed, 68 insertions(+) create mode 100644 .github/ISSUE_TEMPLATE/pull_request_template.md diff --git a/.github/ISSUE_TEMPLATE/pull_request_template.md b/.github/ISSUE_TEMPLATE/pull_request_template.md new file mode 100644 index 0000000..57f6041 --- /dev/null +++ b/.github/ISSUE_TEMPLATE/pull_request_template.md @@ -0,0 +1,68 @@ +## ๐Ÿ”— Related Issue(s) + + + +Closes # + +--- + +## ๐Ÿ“ Description + + + +## ๐Ÿ—๏ธ Type of Change + + + +- [ ] ๐Ÿ› Bug fix (non-breaking change that fixes an issue) +- [ ] โœจ New feature (non-breaking change that adds functionality) +- [ ] ๐Ÿ’ฅ Breaking change (fix or feature that would cause existing functionality to change) +- [ ] ๐Ÿ“œ Smart contract change (Soroban / Rust) +- [ ] ๐ŸŒ Stellar network integration change +- [ ] ๐Ÿ“š Documentation update +- [ ] ๐Ÿ”ง Refactor / code cleanup +- [ ] ๐Ÿงช Test only + +## ๐Ÿงช How Has This Been Tested? + + + +- [ ] Unit tests +- [ ] Integration tests +- [ ] Manual testing on Stellar Testnet +- [ ] Contract simulation (`stellar contract invoke --simulate-only`) + +**Test configuration:** +- Node.js version: +- Network: Testnet / Mainnet +- Relevant wallet address (testnet only): + +## ๐Ÿ“ธ Screenshots / Recordings + + + +## โœ… Checklist + +- [ ] My code follows the project's code style (ESLint + Prettier / Rustfmt) +- [ ] I have performed a self-review of my own code +- [ ] I have commented my code where necessary, particularly in hard-to-understand areas +- [ ] I have made corresponding changes to the documentation +- [ ] My changes generate no new warnings in CI +- [ ] I have added tests that prove my fix is effective or that my feature works +- [ ] All existing tests pass locally +- [ ] For contract changes: I have run `cargo test` and `stellar contract build` +- [ ] I have checked that no secrets or private keys are exposed in this PR + +## ๐Ÿ” Security Considerations + + + +## ๐Ÿ“ฆ Deployment Notes + + + +## ๐Ÿ”— Additional Context + + From d02ba4571edc547e2bea3ad939887c7816e7ad03 Mon Sep 17 00:00:00 2001 From: Jemimah Date: Tue, 25 Aug 2026 04:50:56 +0100 Subject: [PATCH 6/8] Create pull request template for contributions Added a pull request template to standardize PR submissions. --- .github/pull_request_template.md | 68 ++++++++++++++++++++++++++++++++ 1 file changed, 68 insertions(+) create mode 100644 .github/pull_request_template.md diff --git a/.github/pull_request_template.md b/.github/pull_request_template.md new file mode 100644 index 0000000..57f6041 --- /dev/null +++ b/.github/pull_request_template.md @@ -0,0 +1,68 @@ +## ๐Ÿ”— Related Issue(s) + + + +Closes # + +--- + +## ๐Ÿ“ Description + + + +## ๐Ÿ—๏ธ Type of Change + + + +- [ ] ๐Ÿ› Bug fix (non-breaking change that fixes an issue) +- [ ] โœจ New feature (non-breaking change that adds functionality) +- [ ] ๐Ÿ’ฅ Breaking change (fix or feature that would cause existing functionality to change) +- [ ] ๐Ÿ“œ Smart contract change (Soroban / Rust) +- [ ] ๐ŸŒ Stellar network integration change +- [ ] ๐Ÿ“š Documentation update +- [ ] ๐Ÿ”ง Refactor / code cleanup +- [ ] ๐Ÿงช Test only + +## ๐Ÿงช How Has This Been Tested? + + + +- [ ] Unit tests +- [ ] Integration tests +- [ ] Manual testing on Stellar Testnet +- [ ] Contract simulation (`stellar contract invoke --simulate-only`) + +**Test configuration:** +- Node.js version: +- Network: Testnet / Mainnet +- Relevant wallet address (testnet only): + +## ๐Ÿ“ธ Screenshots / Recordings + + + +## โœ… Checklist + +- [ ] My code follows the project's code style (ESLint + Prettier / Rustfmt) +- [ ] I have performed a self-review of my own code +- [ ] I have commented my code where necessary, particularly in hard-to-understand areas +- [ ] I have made corresponding changes to the documentation +- [ ] My changes generate no new warnings in CI +- [ ] I have added tests that prove my fix is effective or that my feature works +- [ ] All existing tests pass locally +- [ ] For contract changes: I have run `cargo test` and `stellar contract build` +- [ ] I have checked that no secrets or private keys are exposed in this PR + +## ๐Ÿ” Security Considerations + + + +## ๐Ÿ“ฆ Deployment Notes + + + +## ๐Ÿ”— Additional Context + + From 10c39393456f7414c1f85c80fdc935f66478b9a6 Mon Sep 17 00:00:00 2001 From: Jemimah Date: Tue, 25 Aug 2026 04:51:15 +0100 Subject: [PATCH 7/8] Delete .github/ISSUE_TEMPLATE/pull_request_template.md --- .../ISSUE_TEMPLATE/pull_request_template.md | 68 ------------------- 1 file changed, 68 deletions(-) delete mode 100644 .github/ISSUE_TEMPLATE/pull_request_template.md diff --git a/.github/ISSUE_TEMPLATE/pull_request_template.md b/.github/ISSUE_TEMPLATE/pull_request_template.md deleted file mode 100644 index 57f6041..0000000 --- a/.github/ISSUE_TEMPLATE/pull_request_template.md +++ /dev/null @@ -1,68 +0,0 @@ -## ๐Ÿ”— Related Issue(s) - - - -Closes # - ---- - -## ๐Ÿ“ Description - - - -## ๐Ÿ—๏ธ Type of Change - - - -- [ ] ๐Ÿ› Bug fix (non-breaking change that fixes an issue) -- [ ] โœจ New feature (non-breaking change that adds functionality) -- [ ] ๐Ÿ’ฅ Breaking change (fix or feature that would cause existing functionality to change) -- [ ] ๐Ÿ“œ Smart contract change (Soroban / Rust) -- [ ] ๐ŸŒ Stellar network integration change -- [ ] ๐Ÿ“š Documentation update -- [ ] ๐Ÿ”ง Refactor / code cleanup -- [ ] ๐Ÿงช Test only - -## ๐Ÿงช How Has This Been Tested? - - - -- [ ] Unit tests -- [ ] Integration tests -- [ ] Manual testing on Stellar Testnet -- [ ] Contract simulation (`stellar contract invoke --simulate-only`) - -**Test configuration:** -- Node.js version: -- Network: Testnet / Mainnet -- Relevant wallet address (testnet only): - -## ๐Ÿ“ธ Screenshots / Recordings - - - -## โœ… Checklist - -- [ ] My code follows the project's code style (ESLint + Prettier / Rustfmt) -- [ ] I have performed a self-review of my own code -- [ ] I have commented my code where necessary, particularly in hard-to-understand areas -- [ ] I have made corresponding changes to the documentation -- [ ] My changes generate no new warnings in CI -- [ ] I have added tests that prove my fix is effective or that my feature works -- [ ] All existing tests pass locally -- [ ] For contract changes: I have run `cargo test` and `stellar contract build` -- [ ] I have checked that no secrets or private keys are exposed in this PR - -## ๐Ÿ” Security Considerations - - - -## ๐Ÿ“ฆ Deployment Notes - - - -## ๐Ÿ”— Additional Context - - From 2cc5b1f34cf97773f7b1aee5e05685da5fff1f9f Mon Sep 17 00:00:00 2001 From: Jemimah Date: Tue, 25 Aug 2026 04:52:24 +0100 Subject: [PATCH 8/8] Update feature request template sections title --- .github/ISSUE_TEMPLATE/feature_request.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/ISSUE_TEMPLATE/feature_request.md b/.github/ISSUE_TEMPLATE/feature_request.md index 65edf75..d2a0ea3 100644 --- a/.github/ISSUE_TEMPLATE/feature_request.md +++ b/.github/ISSUE_TEMPLATE/feature_request.md @@ -11,7 +11,7 @@ assignees: "" -## ๐Ÿ’ก Proposed Solution +## ๐Ÿ’ก Proposed Solution/Mission