Merge remote-tracking branch 'origin/main' into justin/ci

.github/ISSUE_TEMPLATE/bug_report.yml

@@ -0,0 +1,42 @@
+name: Bug Report
+description: File a bug report.
+title: "[Bug]: "
+labels: ["bug", "triage"]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thanks for taking the time to fill out this bug report!
+  - type: textarea
+    id: what-happened
+    attributes:
+      label: What happened and what did you expect to happen?
+      placeholder: Tell us what you see!
+    validations:
+      required: true
+  - type: textarea
+    id: reproduce
+    attributes:
+      label: Describe how to reproduce the bug
+      placeholder: Step by step method to recreate the issue.
+    validations:
+      required: true
+  - type: input
+    id: Version
+    attributes:
+      label: version
+      description: What version of the software are you using?
+  - type: textarea
+    id: logs
+    attributes:
+      label: Relevant logs or stack trace
+      description: Please copy and paste any relevant output from the code. This will be automatically formatted so no need for backticks.
+      render: shell
+  - type: checkboxes
+    id: terms
+    attributes:
+      label: Code of Conduct
+      description: By submitting this issue, you agree to follow our [Code of Conduct](../../../CODE_OF_CONDUCT.md). 
+      options:
+        - label: I agree to follow this project's Code of Conduct
+          required: true

.github/ISSUE_TEMPLATE/docs_issue.yml

@@ -0,0 +1,31 @@
+name: Docs Issue
+description: Report an error or omission in the documentation.
+title: "[Docs]: "
+labels: ["docs", "triage"]
+body:
+  - type: markdown
+    attributes:
+      value: Thanks for taking the time to let us know how we can improve the docs!
+  - type: input
+    id: docs_page_link
+    attributes:
+      label: What page needs improvement?
+      value: Link a URL
+  - type: textarea
+    id: description
+    attributes:
+      label: Description
+      description: Please describe the way the docs didn't meet your needs.
+  - type: textarea
+    id: remedy
+    attributes:
+      label: Remedy
+      description: Please describe what you think needs to be added or changed for the docs to meet your needs.
+  - type: checkboxes
+    id: terms
+    attributes:
+      label: Code of Conduct
+      description: By submitting this issue, you agree to follow our [Code of Conduct](../../../CODE_OF_CONDUCT.md). 
+      options:
+        - label: I agree to follow this project's Code of Conduct
+          required: true

.github/ISSUE_TEMPLATE/feature_request.yml

@@ -0,0 +1,26 @@
+name: Feature Request
+description: Request an enhancement or new feature
+title: "[Feature]: "
+body:
+  - type: textarea
+    id: inspiration
+    attributes:
+      label: Inspiration
+      description: What are you trying to accomplish but finding hard or not possible?
+      placeholder: What's your end goal?
+    validations:
+      required: true
+  - type: textarea
+    id: valueadd
+    attributes:
+      label: Use Cases and Audiences
+      description: What new possibilities does this feature enable, and what types of users will find it helpful?
+      placeholder: Who is the audience and what new applications would this feature enable?
+  - type: checkboxes
+    id: terms
+    attributes:
+      label: Code of Conduct
+      description: By submitting this issue, you agree to follow our [Code of Conduct](../../../CODE_OF_CONDUCT.md). 
+      options:
+        - label: I agree to follow this project's Code of Conduct
+          required: true

.github/ISSUE_TEMPLATE/unclassified.yml

@@ -0,0 +1,20 @@
+name: Unclassified Issue
+description: Open an issue
+title: "[Unclassified]: "
+labels: ["unclassified", "triage"]
+body:
+  - type: markdown
+    attributes:
+      value: Please open a Feature Request, Docs, or Bug Report issue, but if none of those are applicable you can use this generic form.
+  - type: textarea
+    id: description
+    attributes:
+      label: Issue Description
+  - type: checkboxes
+    id: terms
+    attributes:
+      label: Code of Conduct
+      description: By submitting this issue, you agree to follow our [Code of Conduct](../../../CODE_OF_CONDUCT.md). 
+      options:
+        - label: I agree to follow this project's Code of Conduct
+          required: true

.github/PULL_REQUEST_TEMPLATE/pull_request_template.MD

@@ -0,0 +1,29 @@
+### What kind of change does this PR introduce?** (Bug fix, feature, docs update, ...)
+
+---
+### What is the current behavior? (You can also link to an open issue here)
+
+---
+### What is the new behavior (if this is a feature change or bug fix)
+
+---
+### Does this PR introduce a breaking change?
+If so, please describe what changes users might need to make as a result of this PR.
+
+---
+### Associated Issues
+Give a link to the relevant open issue(s) this PR addresses in this repository and others. If it resolves an issue, use `closes: #ddd`.
+
+---
+### Required for all PRs:
+
+- [ ] I have read and agree to follow the [Code of Conduct](../../../CODE_OF_CONDUCT.md) for this project.
+- [ ] I have read and followed the guidelines in the [Contributor's Guide](../../../CONTRIBUTING.md).
+- [ ] I understand I should follow the guidelines in the [Security Guide](../../../SECURITY.md) for any security-related issues or PRs.
+- [ ] I have checked to ensure there aren't other open [Pull Requests](../../../pulls) for the same update/change.
+- [ ] If applicable, I have written the appropriate tests for my new code.
+- [ ] If applicable, I have updated the appropriate documentation for new, updated, deprecated, or removed functionality.
+- [ ] I have run the linter on my code prior to submitting the PR.
+- [ ] All tests are passing locally for me.
+- [ ] My PR has a valid [Conventional Commits](https://www.conventionalcommits.org/en/v1.0.0/#summary) title
+---

CODE_OF_CONDUCT.md

@@ -0,0 +1,133 @@
+
+# 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, socioeconomic 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.
+
+## 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 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].
+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.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].
+
+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
+[Mozilla CoC]: https://github.com/mozilla/diversity
+[FAQ]: https://www.contributor-covenant.org/faq
+[translations]: https://www.contributor-covenant.org/translations

CONTRIBUTING.md

@@ -0,0 +1,89 @@
+# Contributor Guidelines
+
+## Introduction
+
+Welcome to the Strangelove contributor guidelines. We are excited to have you here and look forward to your contributions!
+Contributors are expected to adhere to the guidelines outlined in this document as well as our [code of conduct](./CODE_OF_CONDUCT.md).
+
+##  Contributing
+
+There are many ways to contribute, from writing tutorials or blog posts, improving the documentation,
+submitting bug reports and feature requests, or writing code which can be incorporated into the project itself.
+
+### Bug Reports
+
+First thing to note is that if you believe you have discovered a security vulnerability *DO NOT* use the public issue tracker.
+Please read our [security policy](./SECURITY.md) for more information on reporting security vulnerabilities.
+
+When creating a bug report, please use the [template](./.github/ISSUE_TEMPLATE/bug_report.yml) and include as much
+detail as possible. At a minimum be sure to include the following:
+- What you were trying to do
+- How the bug can be reproduced
+- What you expected to happen
+- What version of the software you were using
+
+### Feature Requests & Enhancements
+
+Feature requests and other enhancements can be made using the [template](./.github/ISSUE_TEMPLATE/feature_request.yml) provided.
+Please provide as much detail as possible, including the problem you are trying to solve and the solution you would like to see,
+along with possible alternatives you have considered if applicable. Understanding the use cases and the benefits the new feature
+or enhancement would bring to users helps the team to prioritize and implement the feature.
+
+### Doc Changes
+
+Documentation changes are always welcome. If you see a typo, or would like to improve the documentation in any way feel
+free to open a PR. If you are unsure about the changes you would like to make or if the changes go well beyond
+addressing simple grammar mistakes or formatting, open an issue to discuss the changes before opening a PR.
+
+### Opening PRs
+
+When opening new PRs it is advised to open an issue first to discuss the changes you would like to make.
+This helps to ensure that the changes are in line with the project goals and that the team is aware of the changes being made
+so that duplicate efforts are not made and everyone's time is used efficiently.
+
+When opening a PR, please ensure that the PR description includes the issue number that the PR is addressing.
+This helps to ensure that the PR is linked to the issue and that the issue is closed when the PR is merged.
+
+
+### Contributor License Agreement
+
+Before opening a PR, please review LICENSE.md and familiarize yourself with its terms.
+Please be advised that by opening a PR, you are granting Strangelove (or the owner of the relevant repository) a perpetual,
+worldwide, non-exclusive, no-charge, royalty-free, irrevocable license, in copyright and in patent, with respect to your
+Contribution and any portion thereof.
+
+## Getting Started
+
+Before you start contributing, make sure you have the following prerequisites installed:
+
+- [Go](https://golang.org/dl/)
+- [Docker](https://www.docker.com/get-started)
+- [VSCode (recommended editor)](https://code.visualstudio.com/)
+
+To get started, follow these steps:
+
+1. Fork the interchaintest repository to your own GitHub account.
+
+2. Clone your forked repository to your local machine:
+
+   ```sh
+   git clone https://github.com/<Username>/interchaintest.git
+   ```
+
+3. Create a new branch on your fork
+
+    ```sh
+    git checkout -b name/broad-description-of-feature
+    ```
+
+4. Make your changes and commit them with descriptive commit messages. 
+
+5. Test your changes locally with `go test ./...`, or by running the specific test affecting your feature or fix.
+
+6. Push your changes to your GitHub forked repository
+
+    ```sh
+    git push origin name/broad-description-of-feature
+    ```
+
+7. Create a pull request (PR) against the main branch of the interchaintest repository. If the PR is still a work-in-progress, please mark the PR as draft.