Merge pull request #3 from ignite/feat/add-hermes-binary

feat: add hermes binaries

.github/CODEOWNERS

@@ -0,0 +1,7 @@
+# CODEOWNERS: https://help.github.com/articles/about-codeowners/
+
+# Primary repo maintainers
+*       @ilgooz @jeronimoalbi @Pantani
+
+# Docs
+*.md    @ilgooz

.github/ISSUE_TEMPLATE/bug-report.md

@@ -0,0 +1,18 @@
+---
+name: Ignite CLI bug report
+about: Create a report to help us improve
+title: ''
+labels: bug
+assignees: ''
+---
+
+**Describe the bug**
+Tell us what you were doing and provide a clear and concise description of issue you encountered.
+
+**To reproduce**
+Steps to reproduce the behavior:
+1.
+
+**What version are you using?**
+
+Provide the output of the `ignite version` command.

.github/ISSUE_TEMPLATE/feature-request.md

@@ -0,0 +1,19 @@
+---
+name: Ignite CLI feature request
+about: Suggest an idea for this project
+title: ''
+labels: request
+assignees: ''
+
+---
+
+**Is your feature request related to a problem or issue you encountered? 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.
+
+Include other useful information that helps us understand your request.

.github/PULL_REQUEST_TEMPLATE/pull_request_template.md

@@ -0,0 +1,9 @@
+Please make sure to check the following for your PR:
+
+- [ ] This PR complies with the [contributing](../../contributing.md) guidelines.
+- [ ] Reviewed "Files changed" and left comments if necessary
+- [ ] Included relevant documentation changes.
+
+Ignite CLI team only:
+
+- [ ] I have updated the _Unreleased_ section in the changelog.md for my changes.

.github/dependabot.yml

@@ -0,0 +1,17 @@
+# To get started with Dependabot version updates, you'll need to specify which
+# package ecosystems to update and where the package manifests are located.
+# Please see the documentation for all configuration options:
+# https://docs.github.com/github/administering-a-repository/configuration-options-for-dependency-updates
+
+version: 2
+updates:
+  - package-ecosystem: "gomod"
+    directory: "/" # Location of package manifests
+    schedule:
+      interval: "daily"
+      time: "10:00"
+    labels:
+      - "dependencies"
+      - "go"
+      - "Skip-Changelog"
+    open-pull-requests-limit: 0

.github/workflows/janitor.yml

@@ -0,0 +1,16 @@
+name: Janitor
+# Janitor cleans up previous runs that are not completed for a given workflow
+# It cancels Sims and Tests
+# Reference the API https://api.github.com/repos/:org/:repo/actions/workflows to find workflow ids
+on:
+  pull_request:
+
+jobs:
+  cancel:
+    name: "Cancel Previous Runs"
+    runs-on: ubuntu-latest
+    timeout-minutes: 3
+    steps:
+      - uses: styfle/[email protected]
+        with:
+          access_token: ${{ github.token }}

.github/workflows/stats.yaml

@@ -0,0 +1,17 @@
+on:
+  schedule:
+    # Run this once per day, towards the end of the day for keeping the most
+    # recent data point most meaningful (hours are interpreted in UTC).
+    - cron: "0 23 * * *"
+  workflow_dispatch: # Allow for running this manually.
+
+jobs:
+  j1:
+    name: Ignite CLI Repository Statistics
+    runs-on: ubuntu-latest
+    steps:
+      - name: run-ghrs
+        uses: jgehrcke/[email protected]
+        with:
+          ghtoken: ${{ secrets.ghrs_github_api_token }}
+

.github/workflows/test-semantic.yml

@@ -0,0 +1,16 @@
+name: Semantic PR
+
+on:
+  pull_request_target:
+    types:
+      - opened
+      - edited
+      - synchronize
+
+jobs:
+  semantic_pr:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: amannn/[email protected]
+        env:
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}

.gitignore

@@ -0,0 +1,10 @@
+scripts/**/nodetime-*
+dist/
+node_modules
+.DS_Store
+apps/
+.idea
+.vscode
+docs/.vuepress/dist
+build/
+*coverage.*

.golangci.yml

@@ -0,0 +1,48 @@
+run:
+  tests: false
+#   # timeout for analysis, e.g. 30s, 5m, default is 1m
+#   timeout: 5m
+
+linters:
+  disable-all: true
+  enable:
+    - bodyclose
+    - decorder
+    - depguard
+    - dogsled
+    - dupword
+    # - errcheck
+    - errchkjson
+    - errorlint
+    - exhaustive
+    - goconst
+    - gocritic
+    - godot
+    - gofumpt
+    - revive
+    # - gosec
+    - gosimple
+    - govet
+    - grouper
+    - ineffassign
+    # - interfacer
+    - misspell
+    - nakedret
+    - nolintlint
+    - exportloopref
+    - staticcheck
+    - reassign
+    - stylecheck
+    - typecheck
+    - unconvert
+    - tenv
+    - thelper
+    - unused
+    - unparam
+    - misspell
+    # - wrapcheck
+    # - wsl
+
+issues:
+  max-issues-per-linter: 0
+  max-same-issues: 0

Makefile

@@ -0,0 +1,49 @@
+#! /usr/bin/make -f
+
+# Project variables.
+PROJECT_NAME = ignite-files
+
+## govet: Run go vet.
+govet:
+	@echo Running go vet...
+	@go vet ./...
+
+## govulncheck: Run govulncheck
+govulncheck:
+	@echo Running govulncheck...
+	@go run golang.org/x/vuln/cmd/govulncheck ./...
+
+## format: Install and run goimports and gofumpt
+format:
+	@echo Formatting...
+	@go run mvdan.cc/gofumpt -w .
+	@go run golang.org/x/tools/cmd/goimports -w -local github.com/ignite/ignite-files .
+	@go run github.com/tbruyelle/mdgofmt/cmd/mdgofmt -w .
+
+## lint: Run Golang CI Lint.
+lint:
+	@echo Running gocilint...
+	@go run github.com/golangci/golangci-lint/cmd/golangci-lint run --out-format=tab --issues-exit-code=0
+
+.PHONY: govet format lint
+
+## test-unit: Run the unit tests.
+test-unit:
+	@echo Running unit tests...
+	@go test -race -failfast -v ./...
+
+## test: Run unit and integration tests.
+test: govet govulncheck test-unit
+
+.PHONY: test-unit test-integration test
+
+help: Makefile
+	@echo
+	@echo " Choose a command run in "$(PROJECT_NAME)", or just run 'make' for install"
+	@echo
+	@sed -n 's/^##//p' $< | column -t -s ':' |  sed -e 's/^/ /'
+	@echo
+
+.PHONY: help
+
+.DEFAULT_GOAL := install

changelog.md

@@ -0,0 +1,13 @@
+# Changelog
+
+## Unreleased
+
+- [#0003](https://github.com/ignite/ignite-files/pull/3) Add Hermes binaries
+
+### Features
+
+### Changes
+
+### Fixes
+
+

code_of_conduct.md

@@ -0,0 +1,125 @@
+# Contributor Covenant Code of Conduct
+
+## Our pledge
+
+We as members, contributors, and leaders pledge to make participation in our
+community a harassment-free experience for everyone, regardless of age, body
+size, visible or invisible disability, ethnicity, sex characteristics, gender
+identity and expression, level of experience, education, socio-economic status,
+nationality, personal appearance, race, religion, or sexual identity
+and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming,
+diverse, inclusive, and healthy community.
+
+## Our standards
+
+Examples of behavior that contributes to a positive environment for our
+community include:
+
+* Demonstrating empathy and kindness toward other people
+* Being respectful of differing opinions, viewpoints, and experiences
+* Giving and gracefully accepting constructive feedback
+* Accepting responsibility and apologizing to those affected by our mistakes,
+    and learning from the experience
+* Focusing on what is best not just for us as individuals, but for the
+    overall community
+
+Examples of unacceptable behavior include:
+
+* The use of sexualized language or imagery and sexual attention or
+    advances of any kind
+* Trolling, insulting or derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or email
+    address, without their explicit permission
+* Other conduct that could reasonably be considered inappropriate in a
+    professional setting
+
+## Enforcement responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of
+acceptable behavior and will take appropriate and fair corrective action in
+response to any behavior that they deem inappropriate, threatening, offensive,
+or harmful.
+
+Community leaders have the right and responsibility to remove, edit, or reject
+comments, commits, code, wiki edits, issues, and other contributions that are
+not aligned to this Code of Conduct, and will communicate reasons for moderation
+decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when
+an individual is officially representing the community in public spaces.
+Examples of representing our community include using an official e-mail address,
+posting by using an official social media account, or acting as an appointed
+representative at an online or offline event.
+
+## Enforcement
+
+Report instances of abusive, harassing, or otherwise unacceptable behavior to the community leaders responsible for
+enforcement at
+<[email protected]>.
+
+All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the
+reporter of any incident.
+
+## Enforcement guidelines
+
+Community leaders will follow these community impact guidelines in determining
+the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community impact**: Use of inappropriate language or other behavior deemed
+unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing
+clarity around the nature of the violation and an explanation of why the
+behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community impact**: A violation through a single incident or series
+of actions.
+
+**Consequence**: A warning with consequences for continued behavior. No
+interaction with the people involved, including unsolicited interaction with
+those enforcing the Code of Conduct, for a specified period of time. This restriction
+includes avoiding interactions in community spaces as well as external channels
+like social media. Violating these terms may lead to a temporary or
+permanent ban.
+
+### 3. Temporary ban
+
+**Community impact**: A serious violation of community standards, including
+sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public
+communication with the community for a specified period of time. No public or
+private interaction with the people involved, including unsolicited interaction
+with those enforcing the Code of Conduct, is allowed during this period.
+Violating these terms may lead to a permanent ban.
+
+### 4. Permanent ban
+
+**Community impact**: Demonstrating a pattern of violation of community
+standards, including sustained inappropriate behavior, harassment of an
+individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within
+the community.
+
+## Attribution
+
+This Code of Conduct is adapted from
+the [Contributor Covenant](https://www.contributor-covenant.org/version/2/0/code_of_conduct.html).
+
+Community impact guidelines are inspired by [Mozilla's code of conduct
+enforcement ladder](https://github.com/mozilla/diversity).
+
+See the [FAQ](https://www.contributor-covenant.org/faq) for answers to common questions about this code of
+conduct. [Translations](https://www.contributor-covenant.org/translations) are also available.