Repository: fivetran/fivetran_connector_sdk
Pull request #133: feature(repo): added issue templates and code of conduct
Author: login: fivetran-elijahdavis
Created: 2025-05-02T18:29:29Z | Merged: 2025-05-26T05:43:23Z

Added Issue templates and code of conduct


Diff:
diff --git a/.github/ISSUE_TEMPLATE/bug_report.yml b/.github/ISSUE_TEMPLATE/bug_report.yml
new file mode 100644
index 000000000..19e07ae6b
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE/bug_report.yml
@@ -0,0 +1,41 @@
+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: input
+    id: version
+    attributes:
+      label: Connector SDK version
+      description: What version of Connector SDK are you using? You can check the version with 'pip show fivetran-connector-sdk'
+      placeholder: ex. 1.4.0
+    validations:
+      required: false
+  - type: textarea
+    id: what-happened
+    attributes:
+      label: What happened?
+      description: Also tell us, what did you expect to happen?
+      placeholder: Tell us what you see!
+      value: "A bug happened!"
+    validations:
+      required: true
+  - type: textarea
+    id: logs
+    attributes:
+      label: Relevant log output
+      description: Please copy and paste any relevant log output. This will be automatically formatted into code, 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](https://github.com/fivetran/fivetran_connector_sdk/tree/main/CODE_OF_CONDUCT.md) 
+      options:
+        - label: I agree to follow this project's Code of Conduct
+          required: true
diff --git a/.github/ISSUE_TEMPLATE/request.yml b/.github/ISSUE_TEMPLATE/request.yml
new file mode 100644
index 000000000..cd02bc758
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE/request.yml
@@ -0,0 +1,45 @@
+name: Request
+description: Suggest an idea for a Connector SDK project.
+title: "[Request]: "
+labels: ["bug", "enhancement", "documentation", "question", "duplicate", "invalid", "wontfix"]
+
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thanks for taking the time to fill out this Connector SDK request!
+  - type: input
+    id: version
+    attributes:
+      label: Connector SDK version
+      description: What version of Connector SDK are you using? You can check the version with 'pip show fivetran-connector-sdk'
+      placeholder: ex. 1.4.0
+    validations:
+      required: false
+  - type: textarea
+    id: what-happened
+    attributes:
+      label: Is your request related to a problem? Please describe...
+      description: A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
+      placeholder: Tell us what you need!
+      value: "Feature x would be great to help with y."
+    validations:
+      required: true
+  - type: textarea
+    id: solution
+    attributes:
+      label: Describe the solution you'd like
+      description: A clear and concise description of what you want to happen.
+  - type: textarea
+    id: info
+    attributes:
+      label: Additional context
+      description: Add any other context or screenshots about the request here.
+  - type: checkboxes
+    id: terms
+    attributes:
+      label: Code of Conduct
+      description: By submitting this issue, you agree to follow our [Code of Conduct](https://github.com/fivetran/fivetran_connector_sdk/tree/main/CODE_OF_CONDUCT.md) 
+      options:
+        - label: I agree to follow this project's Code of Conduct
+          required: true
diff --git a/CODE_OF_CONDUCT.md b/CODE_OF_CONDUCT.md
new file mode 100644
index 000000000..a5e6995a2
--- /dev/null
+++ b/CODE_OF_CONDUCT.md
@@ -0,0 +1,76 @@
+
+# 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, 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 sdk@fivetran.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.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


Reviews:
user: login: alsnkline
body: LGTM
state: APPROVED
author_association: COLLABORATOR
submitted_at: 2025-05-02T18:30:16Z
user: login: fivetran-sadiemartin
state: APPROVED
author_association: COLLABORATOR
submitted_at: 2025-05-05T15:14:21Z
user: login: varundhall
body: @fivetran-elijahdavis these changes don't follow the standard GitHub YAML structure. Please refer https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository
state: CHANGES_REQUESTED
author_association: COLLABORATOR
submitted_at: 2025-05-06T13:48:42Z
user: login: varundhall
state: CHANGES_REQUESTED
author_association: COLLABORATOR
submitted_at: 2025-05-07T10:15:50Z
user: login: fivetran-elijahdavis
state: COMMENTED
author_association: COLLABORATOR
submitted_at: 2025-05-07T18:05:45Z
user: login: fivetran-elijahdavis
state: COMMENTED
author_association: COLLABORATOR
submitted_at: 2025-05-07T18:05:54Z
user: login: fivetran-elijahdavis
state: COMMENTED
author_association: COLLABORATOR
submitted_at: 2025-05-07T18:07:47Z
user: login: fivetran-elijahdavis
state: COMMENTED
author_association: COLLABORATOR
submitted_at: 2025-05-07T18:07:49Z
user: login: fivetran-elijahdavis
state: COMMENTED
author_association: COLLABORATOR
submitted_at: 2025-05-07T18:08:08Z
user: login: alsnkline
state: COMMENTED
author_association: COLLABORATOR
submitted_at: 2025-05-08T00:56:37Z
user: login: alsnkline
state: COMMENTED
author_association: COLLABORATOR
submitted_at: 2025-05-08T00:57:27Z
user: login: alsnkline
state: COMMENTED
author_association: COLLABORATOR
submitted_at: 2025-05-08T01:00:19Z
user: login: varundhall
state: APPROVED
author_association: COLLABORATOR
submitted_at: 2025-05-23T06:08:46Z
user: login: fivetran-dejantucakov
body: @fivetran-elijahdavis @varundhall LGTM
state: APPROVED
author_association: CONTRIBUTOR
submitted_at: 2025-05-23T07:54:35Z

Review comments:
diff_hunk: @@ -0,0 +1,49 @@
+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: input
+    id: contact
+    attributes:
+      label: Contact Details
+      description: How can we get in touch with you if we need more info?
+      placeholder: ex. email@example.com
path: .github/ISSUE_TEMPLATE/bug_report.yml
user: login: varundhall
body: This is a sensitive detail; people don't feel comfortable sharing the emails publicly. 
created_at: 2025-05-07T10:11:26Z
author_association: COLLABORATOR
diff_hunk: @@ -0,0 +1,49 @@
+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: input
+    id: contact
+    attributes:
+      label: Contact Details
+      description: How can we get in touch with you if we need more info?
+      placeholder: ex. email@example.com
+    validations:
+      required: false
+  - type: input
+    id: version
+    attributes:
+      label: Connector SDK version
+      description: What version of Connector SDK are you using? You can check the version with 'pip show fivetran-connector-sdk' or install the latest version with 'pip install --upgrade fivetran-connector-sdk.'
path: .github/ISSUE_TEMPLATE/bug_report.yml
user: login: varundhall
body: while asking for version we are also telling to upgrade to the latest, which can provide incorrect response. Let's just stick to pip show
created_at: 2025-05-07T10:12:32Z
author_association: COLLABORATOR
diff_hunk: @@ -0,0 +1,49 @@
+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: input
+    id: contact
+    attributes:
+      label: Contact Details
+      description: How can we get in touch with you if we need more info?
+      placeholder: ex. email@example.com
+    validations:
+      required: false
+  - type: input
+    id: version
+    attributes:
+      label: Connector SDK version
+      description: What version of Connector SDK are you using? You can check the version with 'pip show fivetran-connector-sdk' or install the latest version with 'pip install --upgrade fivetran-connector-sdk.'
+      placeholder: ex. 1.4.0
+    validations:
+      required: false
+  - type: textarea
+    id: what-happened
+    attributes:
+      label: What happened?
+      description: Also tell us, what did you expect to happen?
+      placeholder: Tell us what you see!
+      value: "A bug happened!"
+    validations:
+      required: true
+  - type: textarea
+    id: logs
+    attributes:
+      label: Relevant log output
+      description: Please copy and paste any relevant log output. This will be automatically formatted into code, 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](https://example.com). 
path: .github/ISSUE_TEMPLATE/bug_report.yml
user: login: varundhall
body: example.com? Please update or review the AI generated stuff 😄 
created_at: 2025-05-07T10:13:19Z
author_association: COLLABORATOR
diff_hunk: @@ -0,0 +1,49 @@
+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: input
+    id: contact
+    attributes:
+      label: Contact Details
+      description: How can we get in touch with you if we need more info?
+      placeholder: ex. email@example.com
+    validations:
+      required: false
+  - type: input
+    id: version
+    attributes:
+      label: Connector SDK version
+      description: What version of Connector SDK are you using? You can check the version with 'pip show fivetran-connector-sdk' or install the latest version with 'pip install --upgrade fivetran-connector-sdk.'
+      placeholder: ex. 1.4.0
+    validations:
+      required: false
+  - type: textarea
+    id: what-happened
+    attributes:
+      label: What happened?
+      description: Also tell us, what did you expect to happen?
+      placeholder: Tell us what you see!
+      value: "A bug happened!"
+    validations:
+      required: true
+  - type: textarea
+    id: logs
+    attributes:
+      label: Relevant log output
+      description: Please copy and paste any relevant log output. This will be automatically formatted into code, 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](https://example.com). 
+      options:
+        - label: I agree to follow this project's Code of Conduct
path: .github/ISSUE_TEMPLATE/bug_report.yml
user: login: varundhall
body: Do we even have such code of conduct?
created_at: 2025-05-07T10:13:42Z
author_association: COLLABORATOR
diff_hunk: @@ -0,0 +1,53 @@
+name: Request
+description: Suggest an idea for a Connector SDK project.
+title: "[Request]: "
+labels: ["Project", "New Feature"]
path: .github/ISSUE_TEMPLATE/request.yml
user: login: varundhall
body: We should check with Product, which labels they want and how
created_at: 2025-05-07T10:15:08Z
author_association: COLLABORATOR
diff_hunk: @@ -0,0 +1,53 @@
+name: Request
+description: Suggest an idea for a Connector SDK project.
+title: "[Request]: "
+labels: ["Project", "New Feature"]
+
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thanks for taking the time to fill out this Connector SDK request!
+  - type: input
+    id: contact
+    attributes:
+      label: Contact Details
+      description: How can we get in touch with you if we need more info?
+      placeholder: ex. email@example.com
path: .github/ISSUE_TEMPLATE/request.yml
user: login: varundhall
body: same
created_at: 2025-05-07T10:15:19Z
author_association: COLLABORATOR
diff_hunk: @@ -0,0 +1,53 @@
+name: Request
+description: Suggest an idea for a Connector SDK project.
+title: "[Request]: "
+labels: ["Project", "New Feature"]
+
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thanks for taking the time to fill out this Connector SDK request!
+  - type: input
+    id: contact
+    attributes:
+      label: Contact Details
+      description: How can we get in touch with you if we need more info?
+      placeholder: ex. email@example.com
+    validations:
+      required: false
+  - type: input
+    id: version
+    attributes:
+      label: Connector SDK version
+      description: What version of Connector SDK are you using? You can check the version with 'pip show fivetran-connector-sdk' or install the latest version with 'pip install --upgrade fivetran-connector-sdk.'
path: .github/ISSUE_TEMPLATE/request.yml
user: login: varundhall
body: same
created_at: 2025-05-07T10:15:27Z
author_association: COLLABORATOR
diff_hunk: @@ -0,0 +1,53 @@
+name: Request
+description: Suggest an idea for a Connector SDK project.
+title: "[Request]: "
+labels: ["Project", "New Feature"]
+
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thanks for taking the time to fill out this Connector SDK request!
+  - type: input
+    id: contact
+    attributes:
+      label: Contact Details
+      description: How can we get in touch with you if we need more info?
+      placeholder: ex. email@example.com
+    validations:
+      required: false
+  - type: input
+    id: version
+    attributes:
+      label: Connector SDK version
+      description: What version of Connector SDK are you using? You can check the version with 'pip show fivetran-connector-sdk' or install the latest version with 'pip install --upgrade fivetran-connector-sdk.'
+      placeholder: ex. 1.4.0
+    validations:
+      required: false
+  - type: textarea
+    id: what-happened
+    attributes:
+      label: Is your request related to a problem? Please describe...
+      description: A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
+      placeholder: Tell us what you need!
+      value: "Feature x would be great to help with y."
+    validations:
+      required: true
+  - type: textarea
+    id: solution
+    attributes:
+      label: Describe the solution you'd like
+      description: A clear and concise description of what you want to happen.
+  - type: textarea
+    id: info
+    attributes:
+      label: Additional context
+      description: Add any other context or screenshots about the request here.
+  - type: checkboxes
+    id: terms
+    attributes:
+      label: Code of Conduct
+      description: By submitting this issue, you agree to follow our [Code of Conduct](https://example.com). 
+      options:
+        - label: I agree to follow this project's Code of Conduct
+          required: true
path: .github/ISSUE_TEMPLATE/request.yml
user: login: varundhall
body: same
created_at: 2025-05-07T10:15:47Z
author_association: COLLABORATOR
diff_hunk: @@ -0,0 +1,49 @@
+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: input
+    id: contact
+    attributes:
+      label: Contact Details
+      description: How can we get in touch with you if we need more info?
+      placeholder: ex. email@example.com
path: .github/ISSUE_TEMPLATE/bug_report.yml
user: login: fivetran-elijahdavis
body: This will be removed
created_at: 2025-05-07T18:05:44Z
author_association: COLLABORATOR
diff_hunk: @@ -0,0 +1,49 @@
+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: input
+    id: contact
+    attributes:
+      label: Contact Details
+      description: How can we get in touch with you if we need more info?
+      placeholder: ex. email@example.com
+    validations:
+      required: false
+  - type: input
+    id: version
+    attributes:
+      label: Connector SDK version
+      description: What version of Connector SDK are you using? You can check the version with 'pip show fivetran-connector-sdk' or install the latest version with 'pip install --upgrade fivetran-connector-sdk.'
path: .github/ISSUE_TEMPLATE/bug_report.yml
user: login: fivetran-elijahdavis
body: Sounds good
created_at: 2025-05-07T18:05:54Z
author_association: COLLABORATOR
diff_hunk: @@ -0,0 +1,49 @@
+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: input
+    id: contact
+    attributes:
+      label: Contact Details
+      description: How can we get in touch with you if we need more info?
+      placeholder: ex. email@example.com
+    validations:
+      required: false
+  - type: input
+    id: version
+    attributes:
+      label: Connector SDK version
+      description: What version of Connector SDK are you using? You can check the version with 'pip show fivetran-connector-sdk' or install the latest version with 'pip install --upgrade fivetran-connector-sdk.'
+      placeholder: ex. 1.4.0
+    validations:
+      required: false
+  - type: textarea
+    id: what-happened
+    attributes:
+      label: What happened?
+      description: Also tell us, what did you expect to happen?
+      placeholder: Tell us what you see!
+      value: "A bug happened!"
+    validations:
+      required: true
+  - type: textarea
+    id: logs
+    attributes:
+      label: Relevant log output
+      description: Please copy and paste any relevant log output. This will be automatically formatted into code, 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](https://example.com). 
path: .github/ISSUE_TEMPLATE/bug_report.yml
user: login: fivetran-elijahdavis
body: It's an example to start the dialogue with product. So...do we want a code of conduct or not?

 @fivetran-sadiemartin / @alsnkline  - do we want to include a code of conduct or no?



created_at: 2025-05-07T18:07:47Z
author_association: COLLABORATOR
diff_hunk: @@ -0,0 +1,49 @@
+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: input
+    id: contact
+    attributes:
+      label: Contact Details
+      description: How can we get in touch with you if we need more info?
+      placeholder: ex. email@example.com
+    validations:
+      required: false
+  - type: input
+    id: version
+    attributes:
+      label: Connector SDK version
+      description: What version of Connector SDK are you using? You can check the version with 'pip show fivetran-connector-sdk' or install the latest version with 'pip install --upgrade fivetran-connector-sdk.'
+      placeholder: ex. 1.4.0
+    validations:
+      required: false
+  - type: textarea
+    id: what-happened
+    attributes:
+      label: What happened?
+      description: Also tell us, what did you expect to happen?
+      placeholder: Tell us what you see!
+      value: "A bug happened!"
+    validations:
+      required: true
+  - type: textarea
+    id: logs
+    attributes:
+      label: Relevant log output
+      description: Please copy and paste any relevant log output. This will be automatically formatted into code, 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](https://example.com). 
+      options:
+        - label: I agree to follow this project's Code of Conduct
path: .github/ISSUE_TEMPLATE/bug_report.yml
user: login: fivetran-elijahdavis
body: It's an example to start the dialogue with product. So...do we want a code of conduct or not?

 @fivetran-sadiemartin / @alsnkline  - do we want to include a code of conduct or no?
created_at: 2025-05-07T18:07:49Z
author_association: COLLABORATOR
diff_hunk: @@ -0,0 +1,53 @@
+name: Request
+description: Suggest an idea for a Connector SDK project.
+title: "[Request]: "
+labels: ["Project", "New Feature"]
path: .github/ISSUE_TEMPLATE/request.yml
user: login: fivetran-elijahdavis
body: @fivetran-sadiemartin / @alsnkline  - what labels would you like shown in the forms?
created_at: 2025-05-07T18:08:08Z
author_association: COLLABORATOR
diff_hunk: @@ -0,0 +1,49 @@
+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: input
+    id: contact
+    attributes:
+      label: Contact Details
+      description: How can we get in touch with you if we need more info?
+      placeholder: ex. email@example.com
+    validations:
+      required: false
+  - type: input
+    id: version
+    attributes:
+      label: Connector SDK version
+      description: What version of Connector SDK are you using? You can check the version with 'pip show fivetran-connector-sdk' or install the latest version with 'pip install --upgrade fivetran-connector-sdk.'
+      placeholder: ex. 1.4.0
+    validations:
+      required: false
+  - type: textarea
+    id: what-happened
+    attributes:
+      label: What happened?
+      description: Also tell us, what did you expect to happen?
+      placeholder: Tell us what you see!
+      value: "A bug happened!"
+    validations:
+      required: true
+  - type: textarea
+    id: logs
+    attributes:
+      label: Relevant log output
+      description: Please copy and paste any relevant log output. This will be automatically formatted into code, 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](https://example.com). 
+      options:
+        - label: I agree to follow this project's Code of Conduct
path: .github/ISSUE_TEMPLATE/bug_report.yml
user: login: alsnkline
body: Yes we should:
https://chatgpt.com/share/e/681bfcc4-c81c-8006-80d6-026a1fa3aa21
created_at: 2025-05-08T00:56:37Z
author_association: COLLABORATOR
diff_hunk: @@ -0,0 +1,49 @@
+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: input
+    id: contact
+    attributes:
+      label: Contact Details
+      description: How can we get in touch with you if we need more info?
+      placeholder: ex. email@example.com
+    validations:
+      required: false
+  - type: input
+    id: version
+    attributes:
+      label: Connector SDK version
+      description: What version of Connector SDK are you using? You can check the version with 'pip show fivetran-connector-sdk' or install the latest version with 'pip install --upgrade fivetran-connector-sdk.'
+      placeholder: ex. 1.4.0
+    validations:
+      required: false
+  - type: textarea
+    id: what-happened
+    attributes:
+      label: What happened?
+      description: Also tell us, what did you expect to happen?
+      placeholder: Tell us what you see!
+      value: "A bug happened!"
+    validations:
+      required: true
+  - type: textarea
+    id: logs
+    attributes:
+      label: Relevant log output
+      description: Please copy and paste any relevant log output. This will be automatically formatted into code, 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](https://example.com). 
+      options:
+        - label: I agree to follow this project's Code of Conduct
path: .github/ISSUE_TEMPLATE/bug_report.yml
user: login: alsnkline
body: Looks easy to add one based on https://www.contributor-covenant.org/version/2/1/code_of_conduct.html.
created_at: 2025-05-08T00:57:27Z
author_association: COLLABORATOR
diff_hunk: @@ -0,0 +1,53 @@
+name: Request
+description: Suggest an idea for a Connector SDK project.
+title: "[Request]: "
+labels: ["Project", "New Feature"]
path: .github/ISSUE_TEMPLATE/request.yml
user: login: alsnkline
body: didn't we discuss this in our meeting?
how about:
"bug"
"enhancement"
"documentation"
"question"
"duplicate". "invalid", "wontfix"

ChatGPT had a bunch of other suggestions that we likely don't need at first.
created_at: 2025-05-08T01:00:19Z
author_association: COLLABORATOR

PR comments:
user: login: height[bot]
created_at: 2025-05-02T18:29:31Z
body: > Link [Height](https://fivetran.height.app) tasks by mentioning a task ID in the pull request title or commit messages, or description and comments with the keyword `link` (e.g. "Link [RD-123](https://fivetran.atlassian.net/browse/RD-123)").
>
> 💡Tip: You can also use "Close T-X" to automatically close a task when the pull request is merged.
<!-- Sent by Height -->
author_association: NONE
user: login: alsnkline
created_at: 2025-05-02T18:45:11Z
body: @varundhall this is updating the templates for issues (which we are opening)
I think it is safe to merge without your README check.
author_association: COLLABORATOR
user: login: fivetran-elijahdavis
created_at: 2025-05-06T15:39:01Z
body: > @fivetran-elijahdavis these changes don't follow the standard GitHub YAML structure. Please refer https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository

-@varundhall Updated and new format attached
![Screenshot 2025-05-06 at 9 38 06 AM](https://github.com/user-attachments/assets/cc8bb531-695e-41c9-b179-158a4c773084)
![Screenshot 2025-05-06 at 9 38 13 AM](https://github.com/user-attachments/assets/c6665508-8c76-4777-9810-cc1f8ad17085)

author_association: COLLABORATOR
user: login: fivetran-elijahdavis
created_at: 2025-05-06T22:48:35Z
body: @alsnkline @fivetran-sadiemartin  - Should we add something about Save Me Time? 

"Need help getting your first connection up and running quickly?

Our team of Professional Services experts is available to provide free advisory services to help you build your first Connector SDK connection. This includes guidance on setup, troubleshooting, and best practices. To get started, simply file a support ticket."
author_association: COLLABORATOR
user: login: alsnkline
created_at: 2025-05-08T01:03:28Z
body: Re save me time here
I don't think it would make sense - it would drop the conversion for issues for sure.

We currently point back to the docs in a section about support - and have a purple call out at the top of that page. I think that's good enough.
author_association: COLLABORATOR
user: login: fivetran-elijahdavis
created_at: 2025-05-15T00:01:00Z
body: @varundhall  / @alsnkline  - all changes have been added to the templates. The last item is what contact information we put in the code of conduct. Do we use one from CSG or mine?

- Code of conduct added
- Code of conduct link added to both templates.
author_association: COLLABORATOR
user: login: alsnkline
created_at: 2025-05-15T00:07:32Z
body: ~~[developers@fivetran.com](mailto:developers@fivetran.com) is one we could consider using~~  - or [elijah.davis@fivetran.com](mailto:elijah.davis@fivetran.com) for starters.

I'll ask amanda about using developers.
author_association: COLLABORATOR
user: login: alsnkline
created_at: 2025-05-15T00:21:37Z
body: I checked with Amanda she suggested using sdk@fivetran.com which she monitors and is currently only used for new partners submitting requests to the Partner SDK program.

I think that's a perfect address to use for this.
author_association: COLLABORATOR