Add incremental attribution models

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,67 @@
+---
+name: Bug report
+about: Report a bug or an issue you've found with this package
+title: ''
+labels: type:bug
+assignees: ''
+
+---
+
+## Describe the bug
+<!---
+A clear and concise description of what the bug is.
+--->
+
+## Steps to reproduce
+<!---
+In as much detail as possible, please provide steps to reproduce the issue. Sample data that triggers the issue, example model code, etc is all very helpful here.
+--->
+
+## Expected results
+<!---
+A clear and concise description of what you expected to happen.
+--->
+
+## Actual results
+<!---
+A clear and concise description of what actually happens.
+--->
+
+## Screenshots and log output
+<!---
+If applicable, add screenshots or log output to help explain your problem.
+--->
+
+## System information
+**The contents of your `packages.yml` file:**
+```yml
+# contents goes here
+```
+
+**Which database are you using dbt with?**
+- [ ] postgres
+- [ ] redshift
+- [ ] bigquery
+- [ ] snowflake
+- [ ] other (specify: ____________)
+
+**The output of `dbt --version`:**
+```
+<output goes here>
+```
+
+**The operating system you're using:**
+
+
+**The output of `python --version`:**
+
+
+## Additional context
+<!---
+Add any other context about the problem here. For example, if you think you know which line of code is causing the issue.
+--->
+
+## Are you interested in contributing the fix?
+<!---
+Let us know if you want to contribute the fix, and whether would need a hand getting started
+--->

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,25 @@
+---
+name: Feature request
+about: Suggest an idea for this project
+title: ''
+labels: type:enhancement
+assignees: ''
+
+---
+
+## Is your feature request related to a problem? Please describe.
+<!-- A clear and concise description of what the problem is. Ex. I'm always frustrated when [...] -->
+
+## Describe the solution you'd like
+<!-- A clear and concise description of what you want to happen. -->
+
+## Describe alternatives you've considered
+<!-- A clear and concise description of any alternative solutions or features you've considered. -->
+
+## Additional context
+<!-- Add any other context or screenshots about the feature request here. -->
+
+## Are you interested in contributing this feature?
+<!---
+Let us know if you want to contribute the feature, and whether would need a hand getting started
+--->

.github/ISSUE_TEMPLATE/question.md

@@ -0,0 +1,16 @@
+---
+name: Question
+about: A more general question about the package. Consider using discourse if more applicable.
+title: ''
+labels: type:question
+assignees: ''
+
+---
+
+<!-- Please consider if your question would be better placed on the Snowplow Discourse (https://discourse.snowplow.io/) for more open conversations -->
+
+### Question
+<!-- What is your question -->
+
+### Additional context
+<!-- Is this feature database-specific? Which database(s) is/are relevant? Please include any other relevant context here. -->

.github/labels.yml

@@ -0,0 +1,81 @@
+- name: "category:breaking_change"
+  color: '1e1037'
+  description: "A breaking change will be introduced if this issue is completed."
+- name: "category:documentation"
+  color: '3849b8'
+  description: "About the documentation."
+- name: "cla:no"
+  color: '313131'
+  description: "[Auto generated] Snowplow Contributor License Agreement has not been signed."
+- name: "cla:yes"
+  color: 'c1c1c1'
+  description: "[Auto generated] Snowplow Contributor License Agreement has been signed."
+- name: "good first issue"
+  color: '69f6ff'
+  description: "Good issue for a first time contributor."
+- name: "priority:high"
+  color: 'f1ff1d'
+  description: "To fix as soon as possible."
+- name: "priority:low"
+  color: 'ffd0d4'
+  description: "Not on the roadmap."
+- name: "priority:medium"
+  color: 'ff6372'
+  description: "On the roadmap."
+- name: "status:blocked"
+  color: '042e31'
+  description: "Maintainers can't work on this right now."
+- name: "status:completed"
+  color: '0ea417'
+  description: "Completed - but might not be released yet."
+- name: "status:duplicate"
+  color: 'b6e1e3'
+  description: "Duplicates another issue."
+- name: "status:has_pr"
+  color: '0ea462'
+  description: "A PR exists for this issue."
+- name: "status:in_progress"
+  color: '0e9ba4'
+  description: "Maintainers are working on this."
+- name: "status:needs_triage"
+  color: 'b6e3cf'
+  description: "Needs maintainer triage."
+- name: "status:wont_fix"
+  color: '04311d'
+  description: "Can't or won't be fixed."
+- name: "status:info_needed"
+  color: '56B9BF'
+  description: "More information is needed from filer for issue to be actionable"
+- name: "status:do_not_merge"
+  color: 'D93F0B'
+  description: "Flag to denote a Issue or PR which should not yet be merged (usually pending a release)"
+- name: "status:help_wanted"
+  color: '69f6ff'
+  description: "Help is wanted to help solve this issue."
+- name: "type:admin"
+  color: 'fdffd2'
+  description: 'About code or repo management.'
+- name: "type:defect"
+  color: '4c381f'
+  description: 'Bugs or weaknesses. The issue has to contain steps to reproduce.'
+- name: "type:enhancement"
+  color: 'ffbd69'
+  description: 'New features or improvements to existing features.'
+- name: "type:question"
+  color: 'ffebd2'
+  description: "Questions to the maintainers."
+- name: "category:models"
+  color: '6738b8'
+  description: "Related to the models in the package."
+- name: "category:macros"
+  color: 'f1ff1d'
+  description: "Related to the macros in the package."
+- name: "category:tests"
+  color: 'a738b8'
+  description: "Related to the tests in the package."
+- name: "category:other"
+  color: '6372ff'
+  description: "Related to other parts of the package or repo itself."
+#- name: "category:4"
+#  color: '9e62dd'
+#  description: "Desc"

.github/pull_request_template.md

@@ -0,0 +1,69 @@
+<!--
+If this is your first time contributing you will be asked to sign the Individual Contributor License Agreement.
+If you would prefer to read this in advance of submitting your PR you can find it here https://docs.google.com/forms/d/e/1FAIpQLSd89YTDQ1XpTZbj3LpOkquV_h1Y8k9ay3iFbJsZsJrz18I23Q/viewform
+-->
+
+## Description
+
+<!-- 
+Please do not leave this blank 
+This PR [adds/removes/fixes/replaces] the [feature/bug/etc]. 
+-->
+
+## What type of PR is this? (check all applicable)
+
+- [ ] 🍕 Feature
+- [ ] 🐛 Bug Fix
+- [ ] 📝 Documentation Update
+- [ ] 🎨 Style
+- [ ] 🧑‍💻 Code Refactor
+- [ ] 🔥 Performance Improvements
+- [ ] ✅ Test
+- [ ] 🤖 Build
+- [ ] 🔁 CI
+- [ ] 📦 Chore (Release)
+- [ ] ⏩ Revert
+
+## Related Tickets & Documents
+<!-- 
+Please use this format link issue numbers: Fixes #123
+https://docs.github.com/en/free-pro-team@latest/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword 
+-->
+
+## Checklist
+- [ ] 🎉 I have verified that these changes work locally
+- [ ] 💣 Is your change a breaking change?
+- [ ] 📖 I have updated the CHANGELOG.md
+### Added tests?
+
+- [ ] 👍 yes
+- [ ] 🙅 no, because they aren't needed
+- [ ] 🙋 no, because I need help
+
+### Added to documentation?
+
+- [ ] 📓 internal package docs (ymls, macros, readme, if applicable)
+- [ ] 📕 I have raised a [Snowplow documentation](https://github.com/snowplow/documentation) PR if applicable (Link here if required)
+- [ ] 🙅 no documentation needed
+
+## [optional] Are there any post-deployment tasks we need to perform?
+## [optional] What gif best describes this PR or how it makes you feel?
+
+<!-- note: PRs with deleted sections will be marked invalid -->
+
+<!--
+  For Work In Progress Pull Requests, please use the Draft PR feature,
+  see https://github.blog/2019-02-14-introducing-draft-pull-requests/ for further details.
+  
+  For a timely review/response, please avoid force-pushing additional
+  commits if your PR already received reviews or comments.
+  
+  Before submitting a Pull Request, please ensure you've done the following:
+  - 📖 Read the Contributing Guide: https://github.com/snowplow/dbt-snowplow-attribution/blob/main/CONTRIBUTING.md
+-->
+
+<!-- 
+## Release Only Checklist
+- [ ] I have updated the version number in all relevant places
+- [ ] I have changed the release date in the CHANGELOG.md 
+-->

.github/workflows/no-response.yml

@@ -0,0 +1,26 @@
+name: No Response
+
+# Both `issue_comment` and `scheduled` event types are required for this Action
+# to work properly.
+on:
+  issue_comment:
+    types: [created]
+  schedule:
+    # Schedule for 08:00 every day
+    - cron: '0 8 * * *'
+
+jobs:
+  noResponse:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: lee-dohm/[email protected]
+        with:
+          token: ${{ github.token }}
+          daysUntilClose: 14
+          responseRequiredLabel: "status:info_needed"
+          closeComment: >
+            This issue has been automatically closed because there has been no response
+            to our request for more information from the original author within 14 days. With only what
+            is currently in the issue, we don't have enough information
+            to take action. Please comment with this information if you have it to reopen the issue so
+            that we can investigate further.