Initial commit

Co-authored-by: Ahsan Khan <amzahsa@amazon.com>
Co-authored-by: Ang Zhou <angzh@amazon.com>
Co-authored-by: Anqi Pang <anqipans@amazon.com>
Co-authored-by: Hsing-Yu Chen <davidhyc@amazon.com>
Co-authored-by: Justin Alvarez <alvajus@amazon.com>
Co-authored-by: Kevin Li <cnkevin@amazon.com>
Co-authored-by: Monirul Islam <monirulu@amazon.com>
Co-authored-by: Mrudul Harwani <mharwani@amazon.com>
Co-authored-by: Sam Berning <bernings@amazon.com>
Co-authored-by: Vishwas Siravara <siravara@amazon.com>
Co-authored-by: Weike Qu <weikequ@amazon.com>
Co-authored-by: Ziwen Ning <ningziwe@amazon.com>

Author: 13 people

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,14 @@
+Issue #, if available:
+
+*Description of changes:*
+
+*Testing done:*
+
+
+
+- [ ] I've reviewed the guidance in CONTRIBUTING.md
+
+
+#### License Acceptance
+
+By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

.github/dependabot.yml

@@ -0,0 +1,21 @@
+version: 2
+updates:
+- package-ecosystem: "gomod"
+  directory: "/"
+  schedule:
+    interval: "daily"
+  commit-message:
+    # When a dependency is updated,
+    # we want release-please to treat the corresponding commit as a releasable unit
+    # because it may contain a security fix.
+    #
+    # Re. how that is achieved, see `changelog-types` in workflows/release-please.yml.
+    prefix: "build"
+    include: "scope"
+- package-ecosystem: "github-actions"
+  directory: "/"
+  schedule:
+    interval: "daily"
+  commit-message:
+    prefix: "ci"
+    include: "scope"

.github/workflows/ci.yml

@@ -0,0 +1,25 @@
+name: CI
+on:
+  push:
+    branches:
+      - main
+  pull_request:
+    branches:
+      - main
+jobs:
+  go-linter:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v3
+      - uses: actions/setup-go@v3
+        with:
+          go-version-file: go.mod
+          cache: true
+      - name: golangci-lint
+        uses: golangci/golangci-lint-action@v3
+        with:
+          # Pin the version in case all the builds start to fail at the same time.
+          # There may not be an automatic way (e.g., dependabot) to update a specific parameter of a Github Action,
+          # so we will just update it manually whenever it makes sense (e.g., a feature that we want is added).
+          version: v1.50.0
+          args: --fix=false

.github/workflows/lint-pr-title.yml

@@ -0,0 +1,19 @@
+name: "Lint PR Title"
+
+on:
+  # TODO: Change to pull_request_target after the repo is public.
+  pull_request:
+    types:
+      - opened
+      - edited
+      - reopened
+      - synchronize
+
+jobs:
+  main:
+    name: conventional-commit
+    runs-on: ubuntu-latest
+    steps:
+      - uses: amannn/action-semantic-pull-request@v5
+        env:
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}

.github/workflows/release-please.yml

@@ -0,0 +1,43 @@
+on:
+  push:
+    branches:
+      - main
+name: release-please
+jobs:
+  release-please:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: google-github-actions/release-please-action@v3
+        with:
+          release-type: go
+          package-name: finch
+          # Include 'build' in the changelog and
+          # make it a releasable unit (patch version bump) because dependabot PRs uses it.
+          # For more details, see ../dependabot.yml.
+          #
+          # The mapping from type to section comes from conventional-commit-types [1]
+          # which is used by action-semantic-pull-request [2],
+          # which is used by us.
+          #
+          # [1] https://github.com/commitizen/conventional-commit-types/blob/master/index.json
+          # [2] https://github.com/amannn/action-semantic-pull-request/blob/0b14f54ac155d88e12522156e52cb6e397745cfd/README.md?plain=1#L60
+          changelog-types: >
+            [
+              {
+                "type":"feat",
+                "section":"Features",
+                "hidden":false
+              },
+              {
+                "type":"fix",
+                "section":"Bug Fixes",
+                "hidden":false
+              },
+              {
+                "type":"build",
+                "section":"Build System or External Dependencies",
+                "hidden":false
+              }
+            ]
+          # Before we are at v1.0.0
+          bump-minor-pre-major: true

.gitignore

@@ -0,0 +1,2 @@
+.vscode
+*.idea

.golangci.yml

@@ -0,0 +1,60 @@
+# The sections in this file are ordered in the order presented in https://golangci-lint.run/usage/configuration/.
+# The nested fields are ordered alphabetically.
+
+linters-settings:
+  goheader:
+    template-path: copyright_header
+  goimports:
+    local-prefixes: github.com/runfinch/tests
+  gosec:
+    config:
+      G306: "0o644"
+  lll:
+    # 145 is just a lax value as we don't want this to be too strict.
+    line-length: 145
+    tab-width: 4
+  makezero:
+    always: true
+  nolintlint:
+    require-explanation: true
+    require-specific: true
+  stylecheck:
+    # ST1003 is left out because it is a bit opinionated.
+    checks: ["all", "-ST1003"]
+linters:
+  enable:
+    - errname
+    - errorlint
+    - exportloopref
+    - forcetypeassert
+    - gocritic
+    - godot
+    - gofumpt
+    - goheader
+    - goimports
+    - gosec
+    - lll
+    - makezero
+    - misspell
+    - nilerr
+    - nilnil
+    - nolintlint
+    - nosprintfhostport
+    - paralleltest
+    - predeclared
+    - reassign
+    - revive
+    - testableexamples
+    - unconvert
+    - unparam
+    - usestdlibvars
+    # TODO: Enable wastedassign after https://github.com/sanposhiho/wastedassign/issues/41 is fixed.
+    # - wastedassign
+    - whitespace
+    - stylecheck
+issues:
+  # Some checks enabled in the stylecheck setting are disabled by default
+  # (e.g., https://golangci-lint.run/usage/false-positives/#exc0013),
+  # so we need to enable them explicitly here.
+  exclude-use-default: false
+  fix: true

CODE_OF_CONDUCT.md

@@ -0,0 +1,4 @@
+## Code of Conduct
+This project has adopted the [Amazon Open Source Code of Conduct](https://aws.github.io/code-of-conduct).
+For more information see the [Code of Conduct FAQ](https://aws.github.io/code-of-conduct-faq) or contact
+opensource-codeofconduct@amazon.com with any additional questions or comments.

CONTRIBUTING.md

@@ -0,0 +1,59 @@
+# Contributing Guidelines
+
+Thank you for your interest in contributing to our project. Whether it's a bug report, new feature, correction, or additional
+documentation, we greatly value feedback and contributions from our community.
+
+Please read through this document before submitting any issues or pull requests to ensure we have all the necessary
+information to effectively respond to your bug report or contribution.
+
+
+## Reporting Bugs/Feature Requests
+
+We welcome you to use the GitHub issue tracker to report bugs or suggest features.
+
+When filing an issue, please check existing open, or recently closed, issues to make sure somebody else hasn't already
+reported the issue. Please try to include as much information as you can. Details like these are incredibly useful:
+
+* A reproducible test case or series of steps
+* The version of our code being used
+* Any modifications you've made relevant to the bug
+* Anything unusual about your environment or deployment
+
+
+## Contributing via Pull Requests
+Contributions via pull requests are much appreciated. Before sending us a pull request, please ensure that:
+
+1. You are working against the latest source on the *main* branch.
+2. You check existing open, and recently merged, pull requests to make sure someone else hasn't addressed the problem already.
+3. You open an issue to discuss any significant work - we would hate for your time to be wasted.
+
+To send us a pull request, please:
+
+1. Fork the repository.
+2. Modify the source; please focus on the specific change you are contributing. If you also reformat all the code, it will be hard for us to focus on your change.
+3. Ensure local tests pass.
+4. Commit to your fork using clear commit messages.
+5. Send us a pull request, answering any default questions in the pull request interface.
+6. Pay attention to any automated CI failures reported in the pull request, and stay involved in the conversation.
+
+GitHub provides additional document on [forking a repository](https://help.github.com/articles/fork-a-repo/) and
+[creating a pull request](https://help.github.com/articles/creating-a-pull-request/).
+
+
+## Finding contributions to work on
+Looking at the existing issues is a great way to find something to contribute on. As our projects, by default, use the default GitHub issue labels (enhancement/bug/duplicate/help wanted/invalid/question/wontfix), looking at any 'help wanted' issues is a great place to start.
+
+
+## Code of Conduct
+This project has adopted the [Amazon Open Source Code of Conduct](https://aws.github.io/code-of-conduct).
+For more information see the [Code of Conduct FAQ](https://aws.github.io/code-of-conduct-faq) or contact
+opensource-codeofconduct@amazon.com with any additional questions or comments.
+
+
+## Security issue notifications
+If you discover a potential security issue in this project we ask that you notify AWS/Amazon Security via our [vulnerability reporting page](http://aws.amazon.com/security/vulnerability-reporting/). Please do **not** create a public github issue.
+
+
+## Licensing
+
+See the [LICENSE](LICENSE) file for our project's licensing. We will ask you to confirm the licensing of your contribution.