Skip to content

Commit

Permalink
Merge branch 'development' into feat/generate-account-if-not-specified
Browse files Browse the repository at this point in the history
  • Loading branch information
dimartiro authored Mar 21, 2024
2 parents f983d77 + 1b39818 commit 41b76cf
Show file tree
Hide file tree
Showing 289 changed files with 6,127 additions and 3,814 deletions.
28 changes: 28 additions & 0 deletions .github/CONTRIBUTING.md
Original file line number Diff line number Diff line change
Expand Up @@ -164,6 +164,34 @@ The purpose of this section is to outline the standard naming conventions approv
> https://www.freecodecamp.org/news/writing-good-commit-messages-a-practical-guide/
## Merge Process
### In General
A Pull Request (PR) needs to be reviewed and approved by project maintainers.
If a change does not alter any logic (e.g. comments, dependencies, docs), then it may be tagged
`C-simple` and merged faster.
### Labels
The set of labels and their description can be found [here](../docs/docs/repo/labels.md).
To change labels update [labels.yml](./labels.yml) file
### Process
1. Please use our [Pull Request Template](./PULL_REQUEST_TEMPLATE.md) and make sure all relevant
information is reflected in your PR.
2. Please tag each PR with minimum one `S-*` (scope) label. The respective `S-*` labels should signal the
component that was changed, they are also used by downstream users to track changes and to
include these changes properly into their own releases.
3. If you’re still working on your PR, please submit as “Draft”. Once a PR is ready for review change
the status to “Open”, so that the maintainers get to review your PR. Generally PRs should sit for
48 hours in order to garner feedback. It may be merged before if all relevant parties had a look at it.
4. PRs will be able to be merged once all reviewers' comments are addressed and CI is successful.

**Noting breaking changes:**
When breaking APIs, the PR description should mention what was changed alongside some examples on how
to change the code to make it work/compile.

## Contributor Responsibilities

Expand Down
2 changes: 1 addition & 1 deletion .github/PULL_REQUEST_TEMPLATE.md
Original file line number Diff line number Diff line change
Expand Up @@ -18,4 +18,4 @@ go test -tags integration github.com/ChainSafe/gossamer

<!-- Tag a code owner to review your PR -->

@timwu20
@
6 changes: 3 additions & 3 deletions .github/dependabot.yml
Original file line number Diff line number Diff line change
Expand Up @@ -5,16 +5,16 @@ updates:
schedule:
interval: "weekly"
labels:
- "dependencies"
- "S-dependencies"
- package-ecosystem: docker
directory: /
schedule:
interval: "weekly"
labels:
- "dependencies"
- "S-dependencies"
- package-ecosystem: gomod
directory: /
schedule:
interval: "weekly"
labels:
- "dependencies"
- "S-dependencies"
249 changes: 249 additions & 0 deletions .github/labels.yml
Original file line number Diff line number Diff line change
@@ -0,0 +1,249 @@
---
- name: Epic
color: "#3E4B9E"
aliases: []
description: Issue used to track development status of a complex feature, aggregates
several issues

- name: Feature-branch
color: "#8ceac8"
aliases: []
description: pull request from feature branch to origin.

- name: Release
color: "#5319E7"
aliases: []
description: pull request with next release changes.

- name: A-tooBig
color: "#FBCA04"
aliases: []
description: Action needed label. Marks that there is a specific action needed for
issue/PR

# Action/attention needed label. Marks that there is a specific action needed for issue/PR
- name: A-stale
color: "#FBCA04"
aliases: []
description: issue or PR is deprecated and needs to be closed.

- name: A-blocked
color: "#F38160"
aliases: []
description: issue or PR is blocked until something else changes.

- name: A-triage
color: "#FBCA04"
aliases: []
description: issue description needs refactor and/or labeled.

- name: A-debug
color: "#FBCA04"
aliases: []
description: issue requires detective debug work to figure out what's going wrong.

- name: A-design
color: "#FBCA04"
aliases: []
description: issue requires design work to think about how it would best be accomplished.

# Describes the type of issue or pull request.
- name: T-bug
color: "#FEF2C0"
aliases: []
description: this issue covers unexpected and/or wrong behaviour.

- name: T-feat
color: "#FEF2C0"
aliases: []
description: this issue/pr is a new feature or functionality.

- name: T-enhancement
color: "#FEF2C0"
aliases: []
description: this issue/pr covers improvement of existing functionality.

- name: T-refactor
color: "#FEF2C0"
aliases: []
description: this issue/pr covers refactoring of existing code.

- name: T-security
color: "#FEF2C0"
aliases: []
description: this issue/pr covers security sensitive problem.

- name: T-question
color: "#FEF2C0"
aliases: []
description: this issue/PR is a discussion/question. Further information is requested

# Complexity label. We operate only 3 complexity levels.
- name: C-simple
color: "#006B75"
aliases: []
description: Minor changes changes, no additional research needed. Good first issue/review.

- name: C-complex
color: "#006B75"
aliases: []
description: Complex changes across multiple modules. Possibly will require additional
research.

- name: C-chaotic
color: "#006B75"
aliases: []
description: Unpredictable nature of this task/changes makes its chaotic.

# Priority level. We only have 3 priority levels, everything else is average by default.
- name: P-critical
color: "#d93f0b"
aliases: []
description: this must be fixed immediately or contributors or users will be severely
impacted.

- name: P-high
color: "#FBCA04"
aliases: []
description: this should be addressed ASAP.

- name: P-low
color: "#0E8A16"
aliases: []
description: this is mostly nice to have.

# Scope this work related to, could be multiple, but usually this means that task needs to be break down.
- name: S-sync-westend
color: "#1D76DB"
aliases: []
description: related to particular network syncing.

- name: S-sync-kusama
color: "#1D76DB"
aliases: []
description: related to particular network syncing.

- name: S-sync-polkadot
color: "#1D76DB"
aliases: []
description: related to particular network syncing.

- name: S-sync-paseo
color: "#1D76DB"
aliases: []
description: related to particular network syncing.

- name: S-tests
color: "#1D76DB"
aliases: []
description: issue related to adding new tests.

- name: S-doc
color: "#1D76DB"
aliases: []
description: documentation related.

- name: S-cli
color: "#1D76DB"
aliases: []
description: issue related to Gossamer CLI.

- name: S-ci
color: "#1D76DB"
aliases: []
description: issue related to continuous integration tasks or piplelines.

- name: S-crypto
color: "#1D76DB"
aliases: []
description: issues related to the lib/crypto package.

- name: S-grandpa
color: "#1D76DB"
aliases: []
description: issues related to block finality.

- name: S-babe
color: "#1D76DB"
aliases: []
description: issues related to block production functionality.

- name: S-runtime
color: "#1D76DB"
aliases: []
description: issues related to the lib/runtime package.

- name: S-telemetry
color: "#1D76DB"
aliases: []
description: issue related to node telemetry and metrics reports.

- name: S-rpc
color: "#1D76DB"
aliases: []
description: issues related to the dot/rpc package.

- name: S-scale
color: "#1D76DB"
aliases: []
description: issues related to the pkg/scale package.

- name: S-trie
color: "#1D76DB"
aliases: []
description: issues related to the pkg/trie package.

- name: S-utils
color: "#1D76DB"
aliases: []
description: issues related to all other lib packages.

- name: S-network
color: "#1D76DB"
aliases: []
description: issues related to the dot/network package.

- name: S-state
color: "#1D76DB"
aliases: []
description: issues related to dot/state package.

- name: S-subsystems-overseer
color: "#1D76DB"
aliases: []
description: issues related to Polkadot host overseer functionality.

- name: S-subsystems-collator
color: "#1D76DB"
aliases: []
description: issues related to polkadot host collator subsystem functionality.

- name: S-subsystems-backing
color: "#1D76DB"
aliases: []
description: issues related to polkadot host backing subsystem functionality.

- name: S-subsystems-availability
color: "#1D76DB"
aliases: []
description: issues related to polkadot host availability subsystem functionality.

- name: S-subsystems-disputes
color: "#1D76DB"
aliases: []
description: issues related to polkadot host disputes subsystem functionality.

- name: S-dependencies
color: "#1D76DB"
aliases: []
description: issues related to polkadot host disputes subsystem functionality.

- name: S-infrastructure
color: "#1D76DB"
aliases: []
description: issues related to infrastructure and DevOps.

- name: S-dependencies
color: "#1D76DB"
aliases: []
description: issues related to dependencies changes. Used by dependabot.
10 changes: 5 additions & 5 deletions .github/workflows/build.yml
Original file line number Diff line number Diff line change
Expand Up @@ -45,14 +45,14 @@ jobs:
- uses: actions/checkout@v4

- name: Go build cache
uses: actions/cache@v3
uses: actions/cache@v4
with:
path: ${{ steps.go-cache-paths.outputs.go-build }}
key: ${{ runner.os }}-go-build-${{ hashFiles('**/go.sum') }}
restore-keys: ${{ runner.os }}-go-build

- name: Go modules cache
uses: actions/cache@v3
uses: actions/cache@v4
with:
path: ${{ steps.go-cache-paths.outputs.go-mod }}
key: ${{ runner.os }}-go-mod-${{ hashFiles('**/go.sum') }}
Expand Down Expand Up @@ -80,14 +80,14 @@ jobs:
- uses: actions/checkout@v4

- name: Go build cache
uses: actions/cache@v3
uses: actions/cache@v4
with:
path: ${{ steps.go-cache-paths.outputs.go-build }}
key: ${{ runner.os }}-go-build-${{ hashFiles('**/go.sum') }}
restore-keys: ${{ runner.os }}-go-build

- name: Go modules cache
uses: actions/cache@v3
uses: actions/cache@v4
with:
path: ${{ steps.go-cache-paths.outputs.go-mod }}
key: ${{ runner.os }}-go-mod-${{ hashFiles('**/go.sum') }}
Expand All @@ -103,7 +103,7 @@ jobs:
- name: Generate coverage report
run: |
go test ./... -coverprofile=coverage.out -covermode=atomic -timeout=20m
- uses: codecov/codecov-action@v3.1.4
- uses: codecov/codecov-action@v4.1.0
with:
files: ./coverage.out
flags: unit-tests
Expand Down
2 changes: 1 addition & 1 deletion .github/workflows/checks.yml
Original file line number Diff line number Diff line change
Expand Up @@ -17,7 +17,7 @@ jobs:
runs-on: buildjet-4vcpu-ubuntu-2204
steps:
- name: Cancel Previous Runs
uses: styfle/[email protected].0
uses: styfle/[email protected].1
with:
all_but_latest: true

Expand Down
2 changes: 1 addition & 1 deletion .github/workflows/copyright.yml
Original file line number Diff line number Diff line change
Expand Up @@ -15,7 +15,7 @@ jobs:
runs-on: buildjet-4vcpu-ubuntu-2204
steps:
- name: Cancel Previous Runs
uses: styfle/[email protected].0
uses: styfle/[email protected].1
with:
all_but_latest: true

Expand Down
2 changes: 1 addition & 1 deletion .github/workflows/devnet.yml
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,7 @@ jobs:
runs-on: buildjet-4vcpu-ubuntu-2204
steps:
- name: Cancel Previous Runs
uses: styfle/[email protected].0
uses: styfle/[email protected].1
with:
all_but_latest: true

Expand Down
2 changes: 1 addition & 1 deletion .github/workflows/docker-grandpa.yml
Original file line number Diff line number Diff line change
Expand Up @@ -23,7 +23,7 @@ jobs:
DOCKER_BUILDKIT: "1"
steps:
- name: Cancel Previous Runs
uses: styfle/[email protected].0
uses: styfle/[email protected].1
with:
all_but_latest: true

Expand Down
2 changes: 1 addition & 1 deletion .github/workflows/docker-js.yml
Original file line number Diff line number Diff line change
Expand Up @@ -23,7 +23,7 @@ jobs:
DOCKER_BUILDKIT: "1"
steps:
- name: Cancel Previous Runs
uses: styfle/[email protected].0
uses: styfle/[email protected].1
with:
all_but_latest: true

Expand Down
Loading

0 comments on commit 41b76cf

Please sign in to comment.