🎉 init repo

Author: jcaillon

.dockerignore

@@ -0,0 +1,3 @@
+*
+!src/*
+!tests.d/*

.editorconfig

@@ -0,0 +1,20 @@
+# EditorConfig helps developers define and maintain consistent
+# coding styles between different editors and IDEs
+# editorconfig.org
+
+root = true
+
+[*]
+indent_style             = space
+trim_trailing_whitespace = true
+insert_final_newline     = false
+indent_size = 2
+charset = utf-8
+end_of_line = lf
+
+[*.md]
+trim_trailing_whitespace = false
+
+[*.bat]
+end_of_line = crlf
+

.gitattributes

@@ -0,0 +1,54 @@
+# Explicitly declare text files you want to always be normalized and converted
+# to native line endings on checkout.
+
+# By default, all text files should have the "lf" (Unix) line endings
+* text eol=lf
+
+# Common files
+*.yml text
+*.xml text
+*.yaml text
+*.md text
+*.txt text
+*.json text
+*.editorconfig text
+*.config text
+*.service text
+*.sh text
+*.zsh text
+*.zshrc text
+*.gitconfig text
+*.gitattributes text
+*.dockerignore text
+Dockerfile text
+VERSION text
+
+# docs
+*.css text
+*.html text
+*.js text
+*.ts text
+*.stylelintrc text
+*.scss text
+*.webmanifest text
+*.svg text
+
+# Windows text files that should be normalized to crlf
+*.ps1 text eol=crlf
+*.cmd text eol=crlf
+*.bat text eol=crlf
+
+# Binary files that should not be normalized or diffed
+*.png binary
+*.gif binary
+*.jpg binary
+*.bmp binary
+*.ico binary
+*.ttf binary
+*.pdf binary
+*.7z  binary
+*.zip binary
+
+
+# To list all file extensions present in the repo in ps1:
+# Get-Childitem -Recurse | Select-Object Extension -Unique

.github/ISSUE_TEMPLATE/Bug_Report.yml

@@ -0,0 +1,50 @@
+name: "Bug report 🐛"
+description: Report errors or unexpected behavior
+labels: [bug]
+body:
+- type: markdown
+  attributes:
+    value: |
+      Please make sure to [search for existing issues](https://github.com/jcaillon/valet-additional-commands/issues) before filing a new one!
+
+
+
+- type: input
+  attributes:
+    label: Valet version
+    placeholder: "x.x.x"
+    description: |
+      You can obtain the valet version by running `valet --version`.
+  validations:
+    required: true
+
+- type: input
+  attributes:
+    label: Bash version and OS.
+    placeholder: "5.x.x on windows git bash"
+    description: |
+      You can obtain the bash version by running `bash --version`.
+  validations:
+    required: true
+
+- type: textarea
+  attributes:
+    label: Steps to reproduce
+    placeholder: Tell us the steps required to trigger your bug.
+  validations:
+    required: true
+
+- type: textarea
+  attributes:
+    label: Expected Behavior
+    description: If you want to include screenshots, paste them into the markdown editor below.
+    placeholder: What were you expecting?
+  validations:
+    required: false
+
+- type: textarea
+  attributes:
+    label: Actual Behavior
+    placeholder: What happened instead?
+  validations:
+    required: true

.github/ISSUE_TEMPLATE/Documentation_Issue.md

@@ -0,0 +1,10 @@
+---
+name: "Documentation Issue 📚"
+about: Report issues in our documentation
+title: ''
+labels: documentation
+assignees: ''
+
+---
+
+<!-- Briefly describe which document needs to be corrected and why. -->

.github/ISSUE_TEMPLATE/Feature_Request.md

@@ -0,0 +1,35 @@
+---
+name: "Feature Request/Idea 🚀"
+about: Suggest a new feature or improvement (this does not mean you have to implement
+  it)
+title: ''
+labels: enhancement
+assignees: ''
+
+---
+
+<!-- 
+🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨
+
+I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING:
+1. If I delete this entire template and go my own path, the core team may close my issue without further explanation or engagement.
+2. If I list multiple bugs/concerns in this one issue, the core team may close my issue without further explanation or engagement.
+3. If I write an issue that has many duplicates, the core team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number).
+4. If I leave the title incomplete when filing the issue, the core team may close my issue without further explanation or engagement.
+5. If I file something completely blank in the body, the core team may close my issue without further explanation or engagement.
+
+All good? Then proceed!
+-->
+
+# Description of the new feature/enhancement
+
+<!--
+A clear and concise description of what the problem is that the new feature would solve.
+Describe why and how a user would use this new functionality (if applicable).
+-->
+
+# Proposed technical implementation details (optional)
+
+<!-- 
+A clear and concise description of what you want to happen.
+-->

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,6 @@
+blank_issues_enabled: true
+
+# contact_links:
+#   - name: Microsoft Security Response Center 🔐
+#     url: [email protected]
+#     about: Please report security vulnerabilities to this email address.

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,13 @@
+## Summary of the Pull Request
+
+## References and Relevant Issues
+
+## Detailed Description of the Pull Request / Additional comments
+
+## Validation Steps Performed
+
+## PR Checklist
+
+- [ ] I have implemented the necessary tests for the feature
+- [ ] I have run `valet self test --auto-approve --core-only` and all tests passed
+- [ ] The documentation has been updated (if needed)

.github/workflows/build-image-on-tag.yaml

@@ -0,0 +1,67 @@
+# The workflow build and push a docker image on new tags and the latest branch.
+name: build-image-on-tag
+
+# Controls when the workflow will run
+on:
+  push:
+    tags:
+      - "v*.*.*"
+    branches:
+      - latest
+
+  # Allows you to run this workflow manually from the Actions tab
+  workflow_dispatch:
+
+# A workflow run is made up of one or more jobs that can run sequentially or in parallel
+jobs:
+  # This workflow contains a single job called "build"
+  build-image:
+    # The type of runner that the job will run on
+    runs-on: ubuntu-latest
+
+    # Steps represent a sequence of tasks that will be executed as part of the job
+    steps:
+      - name: Docker meta
+        id: meta
+        uses: docker/metadata-action@v5
+        with:
+          # list of Docker images to use as base name for tags
+          images: |
+            noyacode/dot
+            ghcr.io/jcaillon/dot
+          # generate Docker tags based on the following events/attributes
+          tags: |
+            type=semver,pattern={{version}}
+            type=ref,event=branch
+
+      - name: Set up QEMU
+        uses: docker/setup-qemu-action@v3
+
+      - name: Set up Docker Buildx
+        uses: docker/setup-buildx-action@v3
+
+      - name: Login to Docker Hub
+        if: github.event_name != 'pull_request'
+        uses: docker/login-action@v3
+        with:
+          username: ${{ vars.DOCKERHUB_USERNAME }}
+          password: ${{ secrets.DOCKERHUB_TOKEN }}
+
+      - name: Login to GHCR
+        if: github.event_name != 'pull_request'
+        uses: docker/login-action@v3
+        with:
+          registry: ghcr.io
+          username: ${{ github.repository_owner }}
+          password: ${{ secrets.GITHUB_TOKEN }}
+
+      - name: Checkout repository
+        uses: actions/checkout@v3
+
+      - name: Build and push
+        uses: docker/build-push-action@v6
+        with:
+          context: .
+          push: ${{ github.event_name != 'pull_request' }}
+          tags: ${{ steps.meta.outputs.tags }}
+          labels: ${{ steps.meta.outputs.labels }}

.github/workflows/ci.yaml

@@ -0,0 +1,41 @@
+# This is a basic workflow to help you get started with Actions
+name: CI
+
+# Controls when the workflow will run
+on:
+  # Triggers the workflow on push or pull request events but only for the "main" branch
+  push:
+    branches: [ "main" ]
+    paths-ignore:
+      - 'docs/**'
+  pull_request:
+    branches: [ "main" ]
+    paths-ignore:
+      - 'docs/**'
+
+  # Allows you to run this workflow manually from the Actions tab
+  workflow_dispatch:
+
+# A workflow run is made up of one or more jobs that can run sequentially or in parallel
+jobs:
+  # This workflow contains a single job called "build"
+  build:
+    # The type of runner that the job will run on
+    runs-on: ubuntu-latest
+
+    # Steps represent a sequence of tasks that will be executed as part of the job
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v4
+        with:
+          fetch-depth: 1
+          submodules: recursive
+
+      # Runs our tests
+      - name: Run valet tests
+        run: |
+          chmod +x valet
+          chmod +x valet.d/commands.d/self-build.sh
+          export VALET_CONFIG_ENABLE_COLORS=true
+          export VALET_CONFIG_DISABLE_PROGRESS=true
+          ./valet self test -C