diff --git a/.github/ISSUE_TEMPLATE/bug-report.yml b/.github/ISSUE_TEMPLATE/bug-report.yml deleted file mode 100644 index f5494b313..000000000 --- a/.github/ISSUE_TEMPLATE/bug-report.yml +++ /dev/null @@ -1,84 +0,0 @@ -name: 🐞 Bug -description: Report a bug or an issue you've found with dbt-spark -title: "[Bug] " -labels: ["bug", "triage"] -body: - - type: markdown - attributes: - value: | - Thanks for taking the time to fill out this bug report! - - type: checkboxes - attributes: - label: Is this a new bug in dbt-spark? - 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 in the dbt-core logic, please open an issue in the dbt-core repository. - If this is a bug experienced while using dbt Cloud, please report to [support](mailto:support@getdbt.com). - 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 search to see if an issue already exists for the bug you encountered. - options: - - label: I believe this is a new bug in dbt-spark - required: true - - label: I have searched the existing issues, and I could not find an existing issue for this bug - required: true - - type: textarea - attributes: - label: Current Behavior - description: A concise description of what you're experiencing. - validations: - required: true - - type: textarea - attributes: - label: Expected Behavior - description: A concise description of what you expected to happen. - validations: - required: true - - type: textarea - attributes: - label: Steps To Reproduce - description: Steps to reproduce the behavior. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - id: logs - attributes: - label: Relevant log output - description: | - If applicable, log output to help explain your problem. - render: shell - validations: - required: false - - type: textarea - attributes: - label: Environment - description: | - examples: - - **OS**: Ubuntu 20.04 - - **Python**: 3.9.12 (`python3 --version`) - - **dbt-core**: 1.1.1 (`dbt --version`) - - **dbt-spark**: 1.1.0 (`dbt --version`) - value: | - - OS: - - Python: - - dbt-core: - - dbt-spark: - render: markdown - validations: - required: false - - type: textarea - attributes: - label: Additional Context - description: | - Links? References? Anything that will give us more context about the issue you are encountering! - - Tip: You can attach images or log files by clicking this area to highlight it and then dragging files in. - validations: - required: false diff --git a/.github/ISSUE_TEMPLATE/config.yml b/.github/ISSUE_TEMPLATE/config.yml deleted file mode 100644 index 129ea7779..000000000 --- a/.github/ISSUE_TEMPLATE/config.yml +++ /dev/null @@ -1,14 +0,0 @@ -blank_issues_enabled: false -contact_links: - - name: Ask the community for help - url: https://github.com/dbt-labs/docs.getdbt.com/discussions - 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-spark/discussions - about: Do you have a Big Idea for dbt-spark? Read open discussions, or start a new one - - name: Create an issue for dbt-core - url: https://github.com/dbt-labs/dbt-core/issues/new/choose - about: Report a bug or request a feature for dbt-core diff --git a/.github/ISSUE_TEMPLATE/feature-request.yml b/.github/ISSUE_TEMPLATE/feature-request.yml deleted file mode 100644 index 8c123ba51..000000000 --- a/.github/ISSUE_TEMPLATE/feature-request.yml +++ /dev/null @@ -1,59 +0,0 @@ -name: ✨ Feature -description: Propose a straightforward extension of dbt-spark functionality -title: "[Feature] <title>" -labels: ["enhancement", "triage"] -body: - - type: markdown - attributes: - value: | - Thanks for taking the time to fill out this feature request! - - type: checkboxes - attributes: - label: Is this your first time submitting a feature request? - description: > - 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-spark functionality. - For "big ideas" about future capabilities of dbt-spark, we ask that you open a - [discussion](https://github.com/dbt-labs/dbt-spark/discussions) in the "Ideas" category instead. - 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-spark functionality, rather than a Big Idea better suited to a discussion - required: true - - type: textarea - attributes: - label: Describe the feature - description: A clear and concise description of what you want to happen. - validations: - required: true - - type: textarea - attributes: - label: Describe alternatives you've considered - description: | - A clear and concise description of any alternative solutions or features you've considered. - validations: - required: false - - type: textarea - attributes: - label: Who will this benefit? - description: | - What kind of use case will this feature be useful for? Please be specific and provide examples, this will help us prioritize properly. - validations: - required: false - - type: input - attributes: - label: Are you interested in contributing this feature? - description: Let us know if you want to write some code, and how we can help. - validations: - required: false - - type: textarea - attributes: - label: Anything else? - description: | - Links? References? Anything that will give us more context about the feature you are suggesting! - validations: - required: false diff --git a/.github/ISSUE_TEMPLATE/regression-report.yml b/.github/ISSUE_TEMPLATE/regression-report.yml deleted file mode 100644 index 8b65d6a26..000000000 --- a/.github/ISSUE_TEMPLATE/regression-report.yml +++ /dev/null @@ -1,82 +0,0 @@ -name: ☣️ Regression -description: Report a regression you've observed in a newer version of dbt-spark -title: "[Regression] <title>" -labels: ["bug", "regression", "triage"] -body: - - type: markdown - attributes: - value: | - Thanks for taking the time to fill out this regression report! - - type: checkboxes - attributes: - label: Is this a regression in a recent version of dbt-spark? - description: > - A regression is when documented functionality works as expected in an older version of dbt-spark, - and no longer works after upgrading to a newer version of dbt-spark - options: - - label: I believe this is a regression in dbt-spark functionality - required: true - - label: I have searched the existing issues, and I could not find an existing issue for this regression - required: true - - type: textarea - attributes: - label: Current Behavior - description: A concise description of what you're experiencing. - validations: - required: true - - type: textarea - attributes: - label: Expected/Previous Behavior - description: A concise description of what you expected to happen. - validations: - required: true - - type: textarea - attributes: - label: Steps To Reproduce - description: Steps to reproduce the behavior. - placeholder: | - 1. In this environment... - 2. With this config... - 3. Run '...' - 4. See error... - validations: - required: true - - type: textarea - id: logs - attributes: - label: Relevant log output - description: | - If applicable, log output to help explain your problem. - render: shell - validations: - required: false - - type: textarea - attributes: - label: Environment - description: | - examples: - - **OS**: Ubuntu 20.04 - - **Python**: 3.9.12 (`python3 --version`) - - **dbt-core (working version)**: 1.1.1 (`dbt --version`) - - **dbt-spark (working version)**: 1.1.0 (`dbt --version`) - - **dbt-core (regression version)**: 1.2.0 (`dbt --version`) - - **dbt-spark (regression version)**: 1.2.0 (`dbt --version`) - value: | - - OS: - - Python: - - dbt-core (working version): - - dbt-spark (working version): - - dbt-core (regression version): - - dbt-spark (regression version): - render: markdown - validations: - required: true - - type: textarea - attributes: - label: Additional Context - description: | - Links? References? Anything that will give us more context about the issue you are encountering! - - Tip: You can attach images or log files by clicking this area to highlight it and then dragging files in. - validations: - required: false diff --git a/.github/dependabot.yml b/.github/dependabot.yml deleted file mode 100644 index 2a6f34492..000000000 --- a/.github/dependabot.yml +++ /dev/null @@ -1,8 +0,0 @@ -version: 2 -updates: - # python dependencies - - package-ecosystem: "pip" - directory: "/" - schedule: - interval: "daily" - rebase-strategy: "disabled" diff --git a/.github/pull_request_template.md b/.github/pull_request_template.md deleted file mode 100644 index 11381456a..000000000 --- a/.github/pull_request_template.md +++ /dev/null @@ -1,26 +0,0 @@ -resolves # - -<!--- - 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. - - Example: - resolves #1234 ---> - -### Description - -<!--- - Describe the Pull Request here. Add any references and info to help reviewers - understand your changes. Include any tradeoffs you considered. ---> - -### Checklist - -- [ ] I have read [the contributing guide](https://github.com/dbt-labs/dbt-spark/blob/main/CONTRIBUTING.md) and understand what's expected of me -- [ ] I have signed the [CLA](https://docs.getdbt.com/docs/contributor-license-agreements) -- [ ] 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 -- [ ] I have [opened an issue to add/update docs](https://github.com/dbt-labs/docs.getdbt.com/issues/new/choose), or docs changes are not required/relevant for this PR -- [ ] I have run `changie new` to [create a changelog entry](https://github.com/dbt-labs/dbt-spark/blob/main/CONTRIBUTING.md#Adding-CHANGELOG-Entry) diff --git a/.github/workflows/backport.yml b/.github/workflows/backport.yml deleted file mode 100644 index 8c0355bda..000000000 --- a/.github/workflows/backport.yml +++ /dev/null @@ -1,42 +0,0 @@ - - -# **what?** -# When a PR is merged, if it has the backport label, it will create -# a new PR to backport those changes to the given branch. If it can't -# cleanly do a backport, it will comment on the merged PR of the failure. -# -# Label naming convention: "backport <branch name to backport to>" -# Example: backport 1.0.latest -# -# You MUST "Squash and merge" the original PR or this won't work. - -# **why?** -# Changes sometimes need to be backported to release branches. -# This automates the backporting process - -# **when?** -# Once a PR is "Squash and merge"'d, by adding a backport label, this is triggered - -name: Backport -on: - pull_request: - types: - - labeled - -permissions: - contents: write - pull-requests: write - -jobs: - backport: - name: Backport - runs-on: ubuntu-latest - # Only react to merged PRs for security reasons. - # See https://docs.github.com/en/actions/using-workflows/events-that-trigger-workflows#pull_request_target. - if: > - github.event.pull_request.merged - && contains(github.event.label.name, 'backport') - steps: - - uses: tibdex/backport@v2.0.2 - with: - github_token: ${{ secrets.GITHUB_TOKEN }} diff --git a/.github/workflows/bot-changelog.yml b/.github/workflows/bot-changelog.yml deleted file mode 100644 index 92aff8eb0..000000000 --- a/.github/workflows/bot-changelog.yml +++ /dev/null @@ -1,60 +0,0 @@ -# **what?** -# When bots create a PR, this action will add a corresponding changie yaml file to that -# PR when a specific label is added. -# -# The file is created off a template: -# -# kind: <per action matrix> -# body: <PR title> -# time: <current timestamp> -# custom: -# Author: <PR User Login (generally the bot)> -# PR: <PR number> -# -# **why?** -# Automate changelog generation for more visability with automated bot PRs. -# -# **when?** -# Once a PR is created, label should be added to PR before or after creation. You can also -# manually trigger this by adding the appropriate label at any time. -# -# **how to add another bot?** -# Add the label and changie kind to the include matrix. That's it! -# - -name: Bot Changelog - -on: - pull_request: - # catch when the PR is opened with the label or when the label is added - types: [labeled] - -permissions: - contents: write - pull-requests: read - -jobs: - generate_changelog: - strategy: - matrix: - include: - - label: "dependencies" - changie_kind: "Dependencies" - - label: "snyk" - changie_kind: "Security" - runs-on: ubuntu-latest - - steps: - - - name: Create and commit changelog on bot PR - if: ${{ contains(github.event.pull_request.labels.*.name, matrix.label) }} - id: bot_changelog - uses: emmyoop/changie_bot@v1.0.1 - with: - GITHUB_TOKEN: ${{ secrets.FISHTOWN_BOT_PAT }} - commit_author_name: "Github Build Bot" - commit_author_email: "<buildbot@fishtownanalytics.com>" - commit_message: "Add automated changelog yaml from template for bot PR" - changie_kind: ${{ matrix.changie_kind }} - label: ${{ matrix.label }} - custom_changelog_string: "custom:\n Author: ${{ github.event.pull_request.user.login }}\n PR: ${{ github.event.pull_request.number }}" diff --git a/.github/workflows/changelog-existence.yml b/.github/workflows/changelog-existence.yml deleted file mode 100644 index 6e51e8afc..000000000 --- a/.github/workflows/changelog-existence.yml +++ /dev/null @@ -1,41 +0,0 @@ -# **what?** -# Checks that a file has been committed under the /.changes directory -# as a new CHANGELOG entry. Cannot check for a specific filename as -# it is dynamically generated by change type and timestamp. -# This workflow should not require any secrets since it runs for PRs -# from forked repos. -# By default, secrets are not passed to workflows running from -# a forked repo. - -# **why?** -# Ensure code change gets reflected in the CHANGELOG. - -# **when?** -# This will run for all PRs going into main and *.latest. It will -# run when they are opened, reopened, when any label is added or removed -# and when new code is pushed to the branch. The action will then get -# skipped if the 'Skip Changelog' label is present is any of the labels. - -name: Check Changelog Entry - -on: - pull_request: - types: [opened, reopened, labeled, unlabeled, synchronize] - workflow_dispatch: - -defaults: - run: - shell: bash - -permissions: - contents: read - pull-requests: write - - -jobs: - changelog: - uses: dbt-labs/actions/.github/workflows/changelog-existence.yml@main - with: - 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-spark contributing guide](https://github.com/dbt-labs/dbt-spark/blob/main/CONTRIBUTING.MD).' - skip_label: 'Skip Changelog' - secrets: inherit # this is only acceptable because we own the action we're calling diff --git a/.github/workflows/jira-creation.yml b/.github/workflows/jira-creation.yml deleted file mode 100644 index b4016befc..000000000 --- a/.github/workflows/jira-creation.yml +++ /dev/null @@ -1,26 +0,0 @@ -# **what?** -# Mirrors issues into Jira. Includes the information: title, -# GitHub Issue ID and URL - -# **why?** -# Jira is our tool for tracking and we need to see these issues in there - -# **when?** -# On issue creation or when an issue is labeled `Jira` - -name: Jira Issue Creation - -on: - issues: - types: [opened, labeled] - -permissions: - issues: write - -jobs: - call-label-action: - uses: dbt-labs/jira-actions/.github/workflows/jira-creation.yml@main - secrets: - JIRA_BASE_URL: ${{ secrets.JIRA_BASE_URL }} - JIRA_USER_EMAIL: ${{ secrets.JIRA_USER_EMAIL }} - JIRA_API_TOKEN: ${{ secrets.JIRA_API_TOKEN }} diff --git a/.github/workflows/jira-label.yml b/.github/workflows/jira-label.yml deleted file mode 100644 index 3da2e3a38..000000000 --- a/.github/workflows/jira-label.yml +++ /dev/null @@ -1,26 +0,0 @@ -# **what?** -# Calls mirroring Jira label Action. Includes adding a new label -# to an existing issue or removing a label as well - -# **why?** -# Jira is our tool for tracking and we need to see these labels in there - -# **when?** -# On labels being added or removed from issues - -name: Jira Label Mirroring - -on: - issues: - types: [labeled, unlabeled] - -permissions: - issues: read - -jobs: - call-label-action: - uses: dbt-labs/jira-actions/.github/workflows/jira-label.yml@main - secrets: - JIRA_BASE_URL: ${{ secrets.JIRA_BASE_URL }} - JIRA_USER_EMAIL: ${{ secrets.JIRA_USER_EMAIL }} - JIRA_API_TOKEN: ${{ secrets.JIRA_API_TOKEN }} diff --git a/.github/workflows/jira-transition.yml b/.github/workflows/jira-transition.yml deleted file mode 100644 index ed9f9cd4f..000000000 --- a/.github/workflows/jira-transition.yml +++ /dev/null @@ -1,24 +0,0 @@ -# **what?** -# Transition a Jira issue to a new state -# Only supports these GitHub Issue transitions: -# closed, deleted, reopened - -# **why?** -# Jira needs to be kept up-to-date - -# **when?** -# On issue closing, deletion, reopened - -name: Jira Issue Transition - -on: - issues: - types: [closed, deleted, reopened] - -jobs: - call-label-action: - uses: dbt-labs/jira-actions/.github/workflows/jira-transition.yml@main - secrets: - JIRA_BASE_URL: ${{ secrets.JIRA_BASE_URL }} - JIRA_USER_EMAIL: ${{ secrets.JIRA_USER_EMAIL }} - JIRA_API_TOKEN: ${{ secrets.JIRA_API_TOKEN }} diff --git a/.github/workflows/main.yml b/.github/workflows/main.yml index f45a30bbc..ca160f40e 100644 --- a/.github/workflows/main.yml +++ b/.github/workflows/main.yml @@ -15,12 +15,6 @@ name: Tests and Code Checks on: - push: - branches: - - "main" - - "*.latest" - - "releases/*" - pull_request: workflow_dispatch: permissions: read-all diff --git a/.github/workflows/stale.yml b/.github/workflows/stale.yml deleted file mode 100644 index a56455d55..000000000 --- a/.github/workflows/stale.yml +++ /dev/null @@ -1,15 +0,0 @@ -name: 'Close stale issues and PRs' -on: - schedule: - - cron: "30 1 * * *" -jobs: - stale: - runs-on: ubuntu-latest - steps: - # pinned at v4 (https://github.com/actions/stale/releases/tag/v4.0.0) - - uses: actions/stale@cdf15f641adb27a71842045a94023bef6945e3aa - with: - stale-issue-message: "This issue has been marked as Stale because it has been open for 180 days with no activity. If you would like the issue to remain open, please remove the stale label or comment on the issue, or it will be closed in 7 days." - stale-pr-message: "This PR has been marked as Stale because it has been open for 180 days with no activity. If you would like the PR to remain open, please remove the stale label or comment on the PR, or it will be closed in 7 days." - # mark issues/PRs stale when they haven't seen activity in 180 days - days-before-stale: 180