Skip to content

Commit

Permalink
Merge pull request #287 from tendermint/release/v0.1.0
Browse files Browse the repository at this point in the history
Release/v0.1.0
  • Loading branch information
lumtis authored Sep 2, 2021
2 parents 5cc6253 + 14cf841 commit d513001
Show file tree
Hide file tree
Showing 918 changed files with 403,145 additions and 6 deletions.
68 changes: 68 additions & 0 deletions .codecov.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,68 @@
coverage:
range: 70...100
round: down
precision: 2
status:
patch: off
changes: false
project:
default:
threshold: 1% # allow this much decrease on project
modules:
if_ci_failed: error
target: 70%
flags:
- modules
client:
if_ci_failed: error
target: 70%
flags:
- client

comment:
layout: "reach, diff, files"
behavior: default
require_changes: false

flags:
modules:
carryforward: true
paths:
- "x/"
- "!x/**/client/**/*"
client:
carryforward: true
paths:
- "x/**/client/**/*"

ignore:
- "x/**/client/cli/query.go"
- "x/**/client/cli/query_params.go"
- "x/**/client/cli/tx.go"
- "x/**/client/cli/tx_*.go"
- "x/**/keeper/keeper.go"
- "x/**/keeper/msg_server.go"
- "x/**/keeper/grpc_query_params.go"
- "x/**/types/codec.go"
- "x/**/types/errors.go"
- "x/**/types/keys.go"
- "x/**/types/key_*.go"
- "x/**/types/types.go"
- "x/**/module.go"
- "x/**/handler.go"
- "*.proto"
- "*.md"
- "*.yml"
- "*.yaml"
- "*.pb.go"
- ".github/"
- "app/"
- "cmd/"
- "docs/"
- "pkg/errors/"
- "proto/"
- "scripts/"
- "tests/"
- "testutil/"
- "dart/"
- "vue/"
7 changes: 7 additions & 0 deletions .github/CODEOWNERS
Validating CODEOWNERS rules …
Original file line number Diff line number Diff line change
@@ -0,0 +1,7 @@
# CODEOWNERS: https://help.github.com/articles/about-codeowners/

# Docs
*.md @barriebyron

# Primary repo maintainers
* @fadeev @ilgooz @lubtd @Pantani
45 changes: 45 additions & 0 deletions .github/CONTRIBUTING.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,45 @@
# Contributing guidelines

If you're willing to create a new PR on Starport Network, make sure that you read and comply with this document.

Start a new [Discussion](https://github.com/tendermint/spn/discussions/new) if you want to propose changes to this document.

Thank you for your contribution!

## Providing Feedback

* Before you open an issue, do a web search, and check for [existing open and closed GitHub Issues](https://github.com/tendermint/spn/issues) to see if your question has already been asked and answered. If you find a relevant topic, you can comment on that issue.
* To provide feedback or ask a question, create a [GitHub issue](https://github.com/tendermint/spn/issues/new/choose). Be sure to provide the relevant information, case study, or informative links as suggested by the Pull Request template.
* We recommend using GitHub issues for issues and feedback. However, you can ask quick questions on the [#🔨cosmos-sdk-starport](https://discord.com/channels/669268347736686612/737461683588431924) channel in Discord.

## Opening pull requests

### Choose a good PR title

Avoid long names in your PR titles. Make sure your title has fewer than 60 characters.

Follow [Conventional Commits](https://www.conventionalcommits.org/en/v1.0.0/) guidelines and keywords to find the best title.

Use parentheses to identify the package or feature that you worked on. For example: `feat(services/chain)`, `fix(scaffolding)`.

### Review your own code

Make sure that you manually tested the changes you're introducing before creating a PR or pushing another commit.

Monitor your PR to make sure that all CI checks pass and the PR shows **All checks have passed** (the checkmark is green).

### Avoid rebasing commits in your branch

Avoid rebasing after you open your PRs to reviews. Instead, add more commits to your PR. It's OK to do force pushes if the PR is still in draft mode and was never opened to reviews before.

A reviewer likes to see a linear commit history while reviewing. If you tend to force push from an older commit, reviewer might lose track in your recent changes and will have to start reviewing from scratch.

Don't worry about adding too many commits. The commits are squashed into a single commit while merging. Your PR title is used as the commit message.

### Ask for help

If you started a PR but couldn't finish it for whatever reason, don't give up. Instead, just ask for help. Someone else can take over and assume the ownership.

We appreciate every bit of your work!

## Coding style
20 changes: 20 additions & 0 deletions .github/ISSUE_TEMPLATE/spn-bug-report.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,20 @@
---
name: Starport Network bug report
about: Create a report to help us improve
title: ''
labels: report
assignees: ''

---

**Describe the bug**
A clear and concise description of what the bug is.

**To Reproduce**
Steps to reproduce the behavior:
1.

**Please provide output of commands**
- `spn version`
- `go version`
- `uname -a`
17 changes: 17 additions & 0 deletions .github/ISSUE_TEMPLATE/spn-feature-request.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,17 @@
---
name: Starport Network feature request
about: Suggest an idea for this project
title: ''
labels: request
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.
21 changes: 21 additions & 0 deletions .github/PULL_REQUEST_TEMPLATE.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,21 @@
<!-- 🎉 Thank you for the PR!!! 🎉 -->

Closes #<issue number>. _in case of a bug fix, this should point to a bug or any other related issue(s)_

### What does this PR does?

<!-- Describe your changes here - ideally you can get that description straight from
your descriptive commit message(s)! -->

### How to test?

<!-- What steps in order should someone run to test -->

## Checklist

These are the criteria that every PR should meet, please check them off as you
review them:

- [ ] Include tests
- [ ] Respect code style and lint
- [ ] Update documentation (*.md) (if needed)
28 changes: 28 additions & 0 deletions .github/workflows/generate.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,28 @@
on: push

jobs:
generate:
runs-on: ubuntu-latest
steps:
- name: Checkout
uses: actions/checkout@v2

- name: Generate Vuex
uses: tendermint/starport/actions/cli@develop
with:
args: g vuex

- name: Generate OpenAPI Docs
uses: tendermint/starport/actions/cli@develop
with:
args: g openapi

# TODO: fix file perm issue
#- name: Create Pull Request
# uses: peter-evans/create-pull-request@v3
# with:
# title: "feat(generate): add generated code"
# commit-message: "feat(generate): add generated code"
# body: ""
# branch: feat/generated
# draft: true
51 changes: 51 additions & 0 deletions .github/workflows/release.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,51 @@
# This workflow is useful if you want to automate the process of:
#
# a) Creating a new prelease when you push a new tag with a "v" prefix (version).
#
# This type of prerelease is meant to be used for production: alpha, beta, rc, etc. types of releases.
# After the prerelease is created, you need to make your changes on the release page at the relevant
# Github page and publish your release.
#
# b) Creating/updating the "latest" prerelease when you push to your default branch.
#
# This type of prelease is useful to make your bleeding-edge binaries available to advanced users.
#
# The workflow will not run if there is no tag pushed with a "v" prefix and no change pushed to your
# default branch.
on: push

jobs:
might_release:
runs-on: ubuntu-latest
steps:
- name: Checkout
uses: actions/checkout@v2

- name: Prepare Release Variables
id: vars
uses: tendermint/starport/actions/release/vars@develop

- name: Issue Release Assets
uses: tendermint/starport/actions/cli@develop
if: ${{ steps.vars.outputs.should_release == 'true' }}
with:
args: chain build --release --release.prefix ${{ steps.vars.outputs.tarball_prefix }} -t linux:amd64 -t darwin:amd64

- name: Delete the "latest" Release
uses: dev-drprasad/delete-tag-and-release@v0.2.0
if: ${{ steps.vars.outputs.is_release_type_latest == 'true' }}
with:
tag_name: ${{ steps.vars.outputs.tag_name }}
delete_release: true
env:
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}

- name: Publish the Release
uses: softprops/action-gh-release@v1
if: ${{ steps.vars.outputs.should_release == 'true' }}
with:
tag_name: ${{ steps.vars.outputs.tag_name }}
files: release/*
prerelease: true
env:
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
31 changes: 31 additions & 0 deletions .github/workflows/test-lint.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,31 @@
name: Lint
on:
pull_request:
push:
branches:
- master
- develop
jobs:
lint:
name: golangci-lint
runs-on: ubuntu-latest
timeout-minutes: 6
steps:
- name: Set up Go
uses: actions/setup-go@v2
with:
go-version: 1.16
- uses: actions/checkout@v2
- uses: technote-space/get-diff-action@v4
with:
PATTERNS: |
**/**.go
go.mod
go.sum
- uses: golangci/golangci-lint-action@master
with:
# Required: the version of golangci-lint is required and must be specified without patch version: we always use the latest patch version.
version: v1.37
args: --issues-exit-code=0 -e SA1019 --timeout 10m
github-token: ${{ secrets.github_token }}
if: env.GIT_DIFF
16 changes: 16 additions & 0 deletions .github/workflows/test-semantic.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,16 @@
name: PR Semantic

on:
pull_request_target:
types:
- opened
- edited
- synchronize

jobs:
semantic_pr:
runs-on: ubuntu-latest
steps:
- uses: amannn/action-semantic-pull-request@v1.2.0
env:
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
26 changes: 26 additions & 0 deletions .github/workflows/test.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,26 @@
name: Unit Tests

on:
pull_request:
push:
branches:
- master
- develop
jobs:
test:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v2

- uses: actions/setup-go@v2
with:
go-version: 1.16

- name: Run unit tests
run: go test -v -coverprofile=coverage.out -covermode=atomic ./...

- name: Upload coverage to Codecov
uses: codecov/codecov-action@v2
with:
fail_ci_if_error: true
verbose: true
13 changes: 7 additions & 6 deletions .gitignore
Original file line number Diff line number Diff line change
@@ -1,7 +1,8 @@
frontend/node_modules
frontend/dist
frontend/.cache
secret.yml
# Code generation
vue/node_modules
vue/dist
release/

# IDE
.idea
.envrc
ansible.cfg
.envrc
33 changes: 33 additions & 0 deletions Makefile
Original file line number Diff line number Diff line change
@@ -0,0 +1,33 @@
#! /usr/bin/make -f

## govet: Run go vet.
govet:
@echo Running go vet...
@go vet ./...

## format: Run gofmt.
format:
@echo Formatting...
@find . -name '*.go' -type f | xargs gofmt -d -s

## lint: Run Golang CI Lint.
lint:
@echo Running gocilint...
@golangci-lint run --out-format=tab --issues-exit-code=0

## test-unit: Run the unit tests.
test-unit:
@echo Running unit tests...
@go test -v ./...

## test: Run unit and integration tests.
test: govet test-unit

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

.DEFAULT_GOAL := install
Loading

0 comments on commit d513001

Please sign in to comment.