Naming things: Repurpose to dbt-cratedb2

.github/ISSUE_TEMPLATE/bug-report.yml

@@ -1,5 +1,5 @@
 name: 🐞 Bug
-description: Report a bug or an issue you've found with dbt-postgres
+description: Report a bug or an issue you've found with dbt-cratedb2
 title: "[Bug] <title>"
 labels: ["bug", "triage"]
 body:
@@ -13,9 +13,10 @@ body:
       description: >
         In other words, is this an error, flaw, failure or fault in our software?
 
-        If this is a bug that broke existing functionality that used to work, please open a regression issue.
-        If this is a bug experienced while using dbt Cloud, please report to [support](mailto:[email protected]).
-        If this is a request for help or troubleshooting code in your own dbt project, please join our [dbt Community Slack](https://www.getdbt.com/community/join-the-community/) or open a [Discussion question](https://github.com/dbt-labs/docs.getdbt.com/discussions).
+        Please report it back to us so we can improve the situation.
+        
+        - [support](mailto:[email protected])
+        - https://cratedb.com/support
 
         Please search to see if an issue already exists for the bug you encountered.
       options:
@@ -62,11 +63,13 @@ body:
         examples:
           - **OS**: Ubuntu 20.04
           - **Python**: 3.11.6 (`python3 --version`)
-          - **dbt-postgres**: 1.0.0 (`dbt --version`)
+          - **dbt-core**: 1.8.7 (`dbt --version`)
+          - **dbt-cratedb2**: 0.1.0 (`dbt --version`)
       value: |
         - OS:
         - Python:
-        - dbt-postgres:
+        - dbt-core:
+        - dbt-cratedb2:
       render: markdown
     validations:
       required: false

.github/ISSUE_TEMPLATE/config.yml

@@ -1,11 +1,11 @@
 blank_issues_enabled: false
 contact_links:
   - name: Ask the community for help
-    url: https://github.com/dbt-labs/docs.getdbt.com/discussions
+    url: https://community.cratedb.com/
     about: Need help troubleshooting? Check out our guide on how to ask
-  - name: Contact dbt Cloud support
-    url: mailto:support@getdbt.com
-    about: Are you using dbt Cloud? Contact our support team for help!
-  - name: Participate in Discussions
-    url: https://github.com/dbt-labs/dbt-postgres/discussions
-    about: Do you have a Big Idea for dbt-postgres? Read open discussions, or start a new one
+  - name: Contact CrateDB Cloud and CrateDB Enterprise support
+    url: https://support.cratedb.com/
+    about: Are you using CrateDB Cloud? Contact our support team for help!
+  - name: General CrateDB support information
+    url: https://cratedb.com/support
+    about: About CrateDB support contacts and knowledge

.github/ISSUE_TEMPLATE/feature-request.yml

@@ -1,5 +1,5 @@
 name: ✨ Feature
-description: Propose a straightforward extension of dbt-postgres functionality
+description: Propose a straightforward extension of dbt-cratedb2 functionality
 title: "[Feature] <title>"
 labels: ["enhancement", "triage"]
 body:
@@ -14,15 +14,12 @@ body:
         We want to make sure that features are distinct and discoverable,
         so that other members of the community can find them and offer their thoughts.
 
-        Issues are the right place to request straightforward extensions of existing dbt-postgres functionality.
-        For "big ideas" about future capabilities of dbt-postgres, we ask that you open a
-        [discussion](https://github.com/dbt-labs/dbt-postgres/discussions/new?category=ideas) in the "Ideas" category instead.
+        Issues are the right place to request straightforward extensions of existing
+        dbt-cratedb2 functionality, or to share other ideas with us.
       options:
-        - label: I have read the [expectations for open source contributors](https://docs.getdbt.com/docs/contributing/oss-expectations)
-          required: true
         - label: I have searched the existing issues, and I could not find an existing issue for this feature
           required: true
-        - label: I am requesting a straightforward extension of existing dbt-postgres functionality, rather than a Big Idea better suited to a discussion
+        - label: I am requesting a straightforward extension of existing dbt-cratedb2 functionality, rather than a Big Idea better suited to a discussion
           required: true
   - type: textarea
     attributes:

.github/ISSUE_TEMPLATE/regression-report.yml

@@ -1,5 +1,5 @@
 name: ☣️ Regression
-description: Report a regression you've observed in a newer version of dbt-postgres
+description: Report a regression you've observed in a newer version of dbt-cratedb2
 title: "[Regression] <title>"
 labels: ["regression", "triage"]
 body:
@@ -57,13 +57,13 @@ body:
         examples:
           - **OS**: Ubuntu 20.04
           - **Python**: 3.11.6 (`python3 --version`)
-          - **dbt-postgres (working version)**: 1.1.0 (`dbt --version`)
-          - **dbt-postgres (regression version)**: 1.2.0 (`dbt --version`)
+          - **dbt-cratedb2 (working version)**: 0.1.0 (`dbt --version`)
+          - **dbt-cratedb2 (regression version)**: 0.2.0 (`dbt --version`)
       value: |
         - OS:
         - Python:
-        - dbt-postgres (working version):
-        - dbt-postgres (regression version):
+        - dbt-cratedb2 (working version):
+        - dbt-cratedb2 (regression version):
       render: markdown
     validations:
       required: true

.github/pull_request_template.md

@@ -1,15 +1,9 @@
 resolves #
-[docs](https://github.com/dbt-labs/docs.getdbt.com/issues/new/choose) dbt-labs/docs.getdbt.com/#
 
 <!---
   Include the number of the issue addressed by this PR above if applicable.
   PRs for code changes without an associated issue *will not be merged*.
   See CONTRIBUTING.md for more information.
-
-  Include the number of the docs issue that was opened for this PR. If
-  this change has no user-facing implications, "N/A" suffices instead. New
-  docs tickets can be created by clicking the link above or by going to
-  https://github.com/dbt-labs/docs.getdbt.com/issues/new/choose.
 -->
 
 ### Problem
@@ -29,7 +23,7 @@ resolves #
 
 ### Checklist
 
-- [ ] I have read [the contributing guide](https://github.com/dbt-labs/dbt-postgres/blob/main/CONTRIBUTING.md) and understand what's expected of me
+- [ ] I have read [the contributing guide](https://github.com/crate-workbench/dbt-cratedb2/blob/main/CONTRIBUTING.md) and understand what's expected of me
 - [ ] I have run this code in development and it appears to resolve the stated issue
 - [ ] This PR includes tests, or tests are not required/relevant for this PR
 - [ ] This PR has no interface changes (e.g. macros, cli, logs, json artifacts, config files, adapter interface, etc) or this PR has already received feedback and approval from Product or DX

.github/workflows/changelog-entry-check.yml

@@ -24,6 +24,6 @@ jobs:
             changelog_comment: >-
                 Thank you for your pull request! We could not find a changelog entry for this change.
                 For details on how to document a change, see the
-                [dbt-postgres contributing guide](https://github.com/dbt-labs/dbt-postgres/blob/main/CONTRIBUTING.md).
+                [dbt-cratedb2 contributing guide](https://github.com/crate-workbench/dbt-cratedb2/blob/main/CONTRIBUTING.md).
             skip_label: "Skip Changelog"
         secrets: inherit

.gitignore

@@ -157,7 +157,7 @@ cython_debug/
 #  be found at https://github.com/github/gitignore/blob/main/Global/JetBrains.gitignore
 #  and can be added to the global gitignore or merged into this file.  For a more nuclear
 #  option (not recommended) you can uncomment the following to ignore the entire idea folder.
-#.idea/
+.idea/
 
 # testing artifacts
 /logs

CHANGELOG.md

@@ -5,38 +5,6 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
 adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html),
 and is generated by [Changie](https://github.com/miniscruff/changie).
 
-## dbt-postgres 1.9.0-b1 - September 25, 2024
+## 0.0.1 - November 12, 2024
 
-### Features
-
-- Add tests for cross-database `cast` macro ([#76](https://github.com/dbt-labs/dbt-postgres/issues/76))
-- Cross-database `date` macro ([#82](https://github.com/dbt-labs/dbt-postgres/issues/82))
-- Add support for Python 3.12 ([#17](https://github.com/dbt-labs/dbt-postgres/issues/17))
-- Allow configuring snapshot column names ([#144](https://github.com/dbt-labs/dbt-postgres/issues/144))
-- Microbatch incremental strategy implementation: merge ([#149](https://github.com/dbt-labs/dbt-postgres/issues/149))
-
-### Fixes
-
-- Fix the semicolon semantics for indexes while respecting other bug fix ([#85](https://github.com/dbt-labs/dbt-postgres/issues/85))
-- Default to psycopg2-binary and allow overriding to psycopg2 via DBT_PSYCOPG2_NAME (restores previous behavior) ([#96](https://github.com/dbt-labs/dbt-postgres/issues/96))
-- Fix `persist_docs` for `materialized_view` materializations. Previously, using this configuration with materialized view models would lead to an error. ([#120](https://github.com/dbt-labs/dbt-postgres/issues/120))
-
-### Under the Hood
-
-- Add support for experimental record/replay testing. ([#123](https://github.com/dbt-labs/dbt-postgres/issues/123))
-- Updating changie.yaml to add contributors and PR links ([#109](https://github.com/dbt-labs/dbt-postgres/issues/109))
-
-### Contributors
-- [@dbeatty10](https://github.com/dbeatty10) ([#76](https://github.com/dbt-labs/dbt-postgres/issues/76), [#82](https://github.com/dbt-labs/dbt-postgres/issues/82))
-- [@gshank](https://github.com/gshank) ([#144](https://github.com/dbt-labs/dbt-postgres/issues/144))
-- [@leahwicz](https://github.com/leahwicz) ([#109](https://github.com/dbt-labs/dbt-postgres/issues/109))
-- [@michelleark](https://github.com/michelleark) ([#149](https://github.com/dbt-labs/dbt-postgres/issues/149))
-- [@mikealfare](https://github.com/mikealfare) ([#17](https://github.com/dbt-labs/dbt-postgres/issues/17), [#96](https://github.com/dbt-labs/dbt-postgres/issues/96))
-- [@morsapaes](https://github.com/morsapaes) ([#120](https://github.com/dbt-labs/dbt-postgres/issues/120))
-- [@peterallenwebb](https://github.com/peterallenwebb) ([#123](https://github.com/dbt-labs/dbt-postgres/issues/123))
-- [@versusfacit](https://github.com/versusfacit) ([#85](https://github.com/dbt-labs/dbt-postgres/issues/85))
-
-
-## Previous Releases
-For information on prior major and minor releases, see their changelogs:
-- [1.8](https://github.com/dbt-labs/dbt-postgres/blob/1.8.latest/CHANGELOG.md)
+- Friendly fork from dbt-postgres 1.9.0-b1 - September 25, 2024