feat: Add repo setup

.editorconfig

@@ -0,0 +1,25 @@
+# Unix-style newlines with a newline ending every file
+[*]
+charset = utf-8
+end_of_line = lf
+indent_size = 2
+indent_style = space
+insert_final_newline = true
+trim_trailing_whitespace = true
+
+[*.{tf,tfvars}]
+indent_size = 2
+indent_style = space
+
+[*.md]
+max_line_length = 0
+trim_trailing_whitespace = false
+
+# Override for Makefile
+[{Makefile, makefile, GNUmakefile, Makefile.*}]
+tab_width = 2
+indent_style = tab
+indent_size = 4
+
+[COMMIT_EDITMSG]
+max_line_length = 0

.gitattributes

@@ -0,0 +1,2 @@
+go.sum merge=union
+*.go text eol=lf

.github/CODEOWNERS

@@ -0,0 +1,12 @@
+# CODEOWNERS file indicates code owners for certain files
+#
+# Code owners will automatically be added as a reviewer for PRs that touch
+# the owned files.
+#
+
+# Default owners for everything in the repo
+#
+# Unless a later match takes precedence, these owners will be requested for
+# review when someone opens a pull request.
+
+* @Excoriate

.github/ISSUE_TEMPLATE/bug_report.md

@@ -0,0 +1,46 @@
+---
+name: 🪲 Bug Report
+about: If something isn't working as expected
+title: "[Bug Title]"
+labels: "bug"
+---
+
+## 🪲 Describe the Bug
+Provide a clear explanation of the bug.
+Example: "The module XYZ crashes when attempting to run the `xyz` command."
+
+## ⚡️ Type of Bug
+Please select the type of bug you are reporting:
+- [ ] Command Error
+- [ ] Crash/Error Message
+- [ ] Installation Issue
+- [ ] Documentation Issue
+- [ ] Other (Please describe)
+
+## 🔬 Steps to Reproduce
+Detail out the steps to reproduce the bug.
+Example:
+1. Run the `xyz` command.
+2. Define the resource parameters.
+3. Observe the crash/error message.
+
+## 🔑 Expected Behavior
+Explain what you anticipated happening.
+
+## 🌚 Actual Behavior
+Describe what actually occurred given the steps.
+
+## 📷 Screenshots
+Include screenshots to better illustrate the bug, if necessary.
+
+## 🧰 Possible Solution
+Impart any insight on a potential bug fix, if possible.
+
+## 📝 Additional Context
+Include any relevant logs, error messages, or related information that would provide more context to the bug.
+
+## 🌪️ Impact
+Provide details on the scale and severity of the bug. This helps determine the urgency of the fix.
+
+## 📚 Related Documentation
+Include any relevant documentation/resources that correlate with the bug.

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,29 @@
+---
+name: ⭐ Feature Request
+about: Propose a great feature idea
+title: "[Feature Title]"
+labels: "enhancement"
+---
+
+## 🌟 Feature Description
+Provide a clear and concise description of the feature you want to suggest.
+For example: "I'd love for the module `xyz` to support the `xyz` command."
+
+## 🚀 What's the Benefit?
+Describe the benefit of implementing the feature from the user's perspective.
+For example: "This feature would speed up the infrastructure setup process by provisioning multiple resources in one command."
+
+## 🛠️ Proposed Solution
+Propose a solution if you have one in mind. If not, just leave this section blank.
+
+## 💡 Possible Alternatives
+If applicable, describe any alternative solutions or features you've considered.
+
+## 🗺️ Example Scenario
+Describe an example where your proposed feature would be beneficial.
+
+## 📚 Any Relevant Documentation?
+Add any relevant documents or links that will help us understand the feature request better.
+
+## 🌞 Anything else you would like to add?
+Add any other context or screenshots about the feature request here!

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,22 @@
+## 🎯 What
+Provide a concise description of the changes:
+* ❓ What changes have you made? (High-level overview)
+* 🎉 What does it mean to the user? (In plain English)
+
+Example:
+* 🚀 Upgraded Terraform AWS provider to v3.0.0.
+* 🎉 This means users can now use new features and improvements from the latest AWS Provider.
+
+## 🤔 Why
+Explain why the changes are necessary:
+* 💡 Why were these changes made?
+* 🎯 What's the benefit?
+
+Example:
+* 💡 We made this upgrade to take advantage of performance improvements and new features in the latest version.
+* 🎯 This will allow us to provision infrastructure more efficiently, and utilize new AWS services and features.
+
+## 📚 References
+Link any supporting context or documentation:
+* 🔗 Github issues, documentation, helpful links.
+* ✅ Use `closes #123`, if this PR closes a GitHub issue `#123`

.github/auto-comment.yml

@@ -0,0 +1,18 @@
+---
+pullRequestOpened: |
+    :wave: Thanks for creating a PR!
+
+    Before we can merge this PR, please make sure that all the following items have been
+    checked off. If any of the checklist items are not applicable, please leave them but
+    write a little note why.
+
+    - [ ] Wrote tests
+    - [ ] Check the CONTRIBUTING guide for other ways to contribute
+    - [ ] Linked to Github issue with discussion and accepted design OR link to spec that
+          describes this work.
+    - [ ] Updated relevant documentation (`docs/`) and code comments
+    - [ ] Re-reviewed `Files changed` in the Github PR explorer
+    - [ ] Applied Appropriate Labels
+
+
+    Thank you for your contribution! :rocket:

.github/config.yml

@@ -0,0 +1,15 @@
+---
+# Configuration for new-issue-welcome - https://github.com/behaviorbot/new-issue-welcome
+# Comment to be posted to on first time issues
+newIssueWelcomeComment: >
+    Thanks for opening your first issue here! 👍 Be sure to follow the issue template.
+
+# Configuration for new-pr-welcome - https://github.com/behaviorbot/new-pr-welcome
+# Comment to be posted to on PRs from first time contributors in your repository
+newPRWelcomeComment: >
+    Thanks for opening this pull request! 👍 Please check out our contributing guidelines.
+
+# Configuration for first-pr-merge - https://github.com/behaviorbot/first-pr-merge
+# Comment to be posted to on pull requests merged by a first time user
+firstPRMergeComment: >
+    Congrats on merging your first pull request! 🎉 We here at `Create Go App` are proud of you.

.github/dependabot.yml

@@ -0,0 +1,12 @@
+---
+version: 2
+updates:
+    - package-ecosystem: gomod
+      directory: /
+      schedule:
+          interval: daily
+          time: 11:00
+      open-pull-requests-limit: 10
+      ignore:
+          - dependency-name: github.com/pterm/pterm
+          - dependency-name: github.com/spf13/cobra

.github/labeler.yml

@@ -0,0 +1,30 @@
+---
+ci/cd:
+    - .github/workflows/*
+infrastructure:
+    - terraform/**
+    - infra/**
+    - modules/**
+    - terragrunt/**
+documentation:
+    - README.md
+    - .github/ISSUE_TEMPLATE/*
+    - ./*.md
+patch:
+    - TaskFile.yml
+    - LICENSE
+    - .github/labeler.yml
+    - .yamllint.yml
+    - .Makefile
+    - .pre-commit-config.yaml
+    - .goreleaser.yml
+    - .github/settings.yml
+    - .github/dependabot.yml
+    - .gitignore
+    - .gitattributes
+    - .shellcheckrc
+    - .editorconfig
+    - .dockerignore
+minor:
+    - pkg/*
+    - cli/*

.github/no-response.yml

@@ -0,0 +1,14 @@
+---
+# Configuration for probot-no-response - https://github.com/probot/no-response
+
+# Number of days of inactivity before an Issue is closed for lack of response
+daysUntilClose: 30
+# Label requiring a response
+responseRequiredLabel: more-information-needed
+# Comment to post when closing an Issue for lack of response. Set to `false` to disable
+closeComment: >-
+    This issue has been automatically closed because there has been no response
+    to our request for more information from the original author. With only the
+    information that is currently in the issue, we don't have enough information
+    to take action. Please feel free to reach out if you have or find the answers we need so
+    that we can investigate further. Thank you!

.github/settings.yml

@@ -0,0 +1,51 @@
+---
+repository:
+    name: daggerverse
+    description: A collection of Dagger modules powered by Dagger.
+    topics: example, devops, tooling, ecs, sre, cli, dagger, ci/cd
+    default_branch: main
+    allow_squash_merge: true
+    allow_merge_commit: true
+    allow_rebase_merge: true
+    delete_branch_on_merge: true
+    has_projects: true
+    has_wiki: false
+    enable_vulnerability_alerts: true
+    enable_automated_security_fixes: true
+    teams:
+        - name: maintainers
+          permission: admin
+        - name: contributors
+          permission: push
+labels:
+    - name: bug
+      color: CC0000
+      description: Something is not working fine 🐛.
+    - name: feature
+      color: '#336699'
+      description: New functionality 🚀.
+    - name: Help Wanted
+      new_name: help wanted 🙏
+    - name: documentation
+      color: 0075ca
+      description: Improvements or additions to documentation 📚.
+branches:
+    - name: main
+      protection:
+          required_pull_request_reviews:
+              required_approving_review_count: 1
+              dismiss_stale_reviews: true
+              require_code_owner_reviews: true
+              dismissal_restrictions: {}
+              code_owner_approval: true
+              required_conversation_resolution: true
+          required_status_checks:
+              strict: true
+              contexts:
+                  - DCO
+          enforce_admins: false
+          required_linear_history: true
+          restrictions:
+              users: [Excoriate]
+              apps: []
+              teams: []

.github/stale.yml

@@ -0,0 +1,22 @@
+---
+# Number of days of inactivity before an issue becomes stale
+daysUntilStale: 10
+# Number of days of inactivity before a stale issue is closed
+daysUntilClose: 3
+# Issues with these labels will never be considered stale
+exemptLabels:
+    - pinned
+    - security
+# Label to use when marking an issue as stale
+staleLabel: wontfix
+# Comment to post when marking an issue as stale. Set to `false` to disable
+markComment: >
+    👋  Hello. Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward?
+
+    > This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.
+
+    Thank you for your contributions.
+
+# Comment to post when closing a stale Issue or Pull Request. Set to `false` to disable
+closeComment: >
+    ⚡️ This issue has been automatically closed because it has not had recent activity.

.github/workflows/go-ci-lint.yaml

@@ -0,0 +1,29 @@
+---
+name: Go Linter
+on:
+    workflow_dispatch:
+    push:
+    pull_request:
+permissions:
+    contents: read
+    pull-requests: read
+jobs:
+    golangci:
+        name: Golangci-lint
+        runs-on: ubuntu-latest
+        env:
+            GO_VERSION: ~1.21
+        steps:
+            - uses: actions/checkout@v3
+            - name: Set up Go
+              uses: actions/setup-go@v4
+              with:
+                  go-version: ${{ env.GO_VERSION }}
+                  cache: false
+            - name: golangci-lint
+              uses: golangci/golangci-lint-action@v3
+              with:
+                  version: v1.54
+                  args: --config .golangci.yml
+                  github_token: ${{ secrets.GITHUB_TOKEN }}
+                  reporter: github-pr-check

.github/workflows/go-ci-tests.yml

@@ -0,0 +1,20 @@
+---
+name: Go Tests
+on:
+    workflow_dispatch:
+    push:
+    pull_request:
+env:
+    GO_VERSION: ~1.21
+jobs:
+    golangci:
+        name: Go Tests
+        runs-on: ubuntu-latest
+        steps:
+            - uses: actions/checkout@v3
+            - name: Set up Go
+              uses: actions/setup-go@v4
+              with:
+                  go-version: ${{ env.GO_VERSION }}
+            - name: Test
+              run: go test -v ./...