feat: bump cosmos-sdk to v0.50.8 and ignite to v28.5.2

.github/CODEOWNERS

@@ -1,7 +1,9 @@
 # CODEOWNERS: https://help.github.com/articles/about-codeowners/
 
 # Primary repo maintainers
-*       @ilgooz @jeronimoalbi @Pantani
+*       @ilgooz @jeronimoalbi @Pantani @julienrbrt
 
 # Docs
-*.md    @ilgooz
+*.md    @salmad3 @toschdev @ilgooz
+docs/*   @salmad3 @toschdev @ilgooz
+changelog.md @ilgooz @salmad3 @toschdev @jeronimoalbi @Pantani @julienrbrt

.github/CONTRIBUTING.md

@@ -0,0 +1,44 @@
+# Contributing guidelines
+
+If you're willing to create a new PR on this repository, make sure that you read and comply with this document.
+
+Start a new [Discussion](https://github.com/tendermint/fundraising/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/fundraising/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/fundraising/issues/new/choose). Be sure to provide the relevant information, case study, or informative links as suggested by the Pull Request template.
+
+## 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(claim)`, `fix(app)`.
+
+### 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

.github/ISSUE_TEMPLATE/bug-report.md

@@ -1,39 +1,21 @@
 ---
-name: Bug Report 
-about: Create a report to help us squash bugs!
+name: Ignite Fundraising bug report
+about: Create a report to help us improve
+title: ''
+labels: report
+assignees: ''
 
 ---
 
-<!-- < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < ☺ 
-v                            ✰  Thanks for opening an issue! ✰    
-v    Before smashing the submit button please review the template.
-v    Please also ensure that this is not a duplicate issue :)  
-☺ > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >  -->
+**Describe the bug**
+A clear and concise description of what the bug is.
 
-## Summary of Bug
+**To Reproduce**
+Steps to reproduce the behavior:
+1.
 
-<!-- Concisely describe the issue -->
-
-## Version
-
-<!-- git commit hash or release version -->
-
-## Steps to Reproduce
-
-<!-- What commands in order should someone run to reproduce your problem? -->
-
-## Tasks
-
-- 
-
-## References
-
--
-____
-
-## For Admin Use
-
-- [ ] Not duplicate issue
-- [ ] Appropriate labels applied
-- [ ] Appropriate contributors tagged
-- [ ] Contributor assigned/self-assigned
+**Please provide output of commands while in the repo base directory**
+- `git rev-parse --verify HEAD`
+- `ignite version`
+- `go version`
+- `uname -a`

.github/ISSUE_TEMPLATE/feature-request.md

@@ -1,43 +1,17 @@
 ---
-name: Feature Request
-about: Create a proposal to request a feature
+name: Ignite Fundraising feature request
+about: Suggest an idea for this project
+title: ''
+labels: request
+assignees: ''
 
 ---
 
-<!-- < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < ☺ 
-v                            ✰  Thanks for opening an issue! ✰    
-v    Before smashing the submit button please review the template.
-v    Word of caution: poorly thought-out proposals may be rejected 
-v                     without deliberation 
-☺ > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >  -->
+**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 [...]
 
-## Summary
+**Describe the solution you'd like**
+A clear and concise description of what you want to happen.
 
-<!-- Short, concise description of the proposed feature -->
-
-## Problem Definition
-
-<!-- Why do we need this feature? 
-What problems may be addressed by introducing this feature?
-What benefits does the SDK stand to gain by including this feature?
-Are there any disadvantages of including this feature? -->
-
-## Proposal
-
-<!-- Detailed description of requirements of implementation -->
-
-## Tasks
-
-- 
-
-## References
-
--
-____
-
-#### For Admin Use
-
-- [ ] Not duplicate issue
-- [ ] Appropriate labels applied
-- [ ] Appropriate contributors tagged
-- [ ] Contributor assigned/self-assigned
+**Describe alternatives you've considered**
+A clear and concise description of any alternative solutions or features you've considered.

.github/PULL_REQUEST_TEMPLATE.md

@@ -1,37 +1,21 @@
-<!-- < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < < ☺
-v                               ✰  Thanks for creating a PR! ✰
-v    Before smashing the submit button please review the checkboxes.
-v    If a checkbox is n/a - please still include it but + a little note why
-☺ > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >  -->
+<!-- 🎉 Thank you for the PR!!! 🎉 -->
 
-## Description
+Closes #<issue number>. _in case of a bug fix, this should point to a bug or any other related issue(s)_
 
-<!-- Add a description of the changes that this PR introduces and the files that
-are the most critical to review.
--->
+### What does this PR do?
 
-closes: #XXXX
+<!-- Describe your changes here - ideally you can get that description straight from
+your descriptive commit message(s)! -->
 
-## Tasks
+### How to test?
 
-- [ ] 
+<!-- What steps in order should someone run to test -->
 
-## References
+## Checklist
 
-- 
+These are the criteria that every PR should meet, please check them off as you
+review them:
 
----
-
-Before we can merge this PR, please make sure that all the following items have been
-checked off. If any of the checklist items are not applicable, please leave them but
-write a little note why.
-
-- [ ] Appropriate labels applied
-- [ ] Targeted PR against correct branch
-- [ ] Linked to Github issue with discussion and accepted design OR link to spec that describes this work.
-- [ ] Code follows the [module structure standards](https://github.com/cosmos/cosmos-sdk/blob/v0.46.0/docs/building-modules/README.md).
-- [ ] Wrote unit and integration
-- [ ] Updated relevant documentation (`docs/`) or specification (`x/<module>/spec/`)
-- [ ] Added relevant `godoc` [comments](https://go.dev/blog/godoc).
-- [ ] Re-reviewed `Files changed` in the Github PR explorer
-- [ ] Review `Codecov Report` in the comment section below once CI passes
+- [ ] Include tests
+- [ ] Respect code style and lint
+- [ ] Update documentation (*.md) (if needed)

.github/codecov.yml

@@ -0,0 +1,75 @@
+coverage:
+  precision: 2
+  round: down
+  range: 70...100
+  status:
+    patch: off
+    changes: false
+    project:
+      default:
+        target: auto
+        threshold: 10%
+        informational: true
+      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
+
+codecov:
+  notify:
+    wait_for_ci: 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/**/keeper/invariants.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"
+  - "x/**/module_simulation.go"
+  - "*.proto"
+  - "*.md"
+  - "*.yml"
+  - "*.yaml"
+  - "*.pb.go"
+  - "*.pb.gw.go"
+  - ".github/"
+  - "app/"
+  - "cmd/"
+  - "docs/"
+  - "proto/"
+  - "scripts/"
+  - "testutil/"
+  - "dart/"
+  - "vue/"

.github/workflows/janitor.yml

@@ -13,5 +13,4 @@ jobs:
     steps:
       - uses: styfle/[email protected]
         with:
-          workflow_id: 24088051,15584120
           access_token: ${{ github.token }}

.github/workflows/linkchecker.yml

@@ -6,14 +6,14 @@ on:
     branches:
       - main
       - develop
-  schedule: 
+  schedule:
     - cron: '* */24 * * *'
 
 jobs:
   markdown-link-check:
     runs-on: ubuntu-latest
     steps:
-      - uses: actions/checkout@v3
+      - uses: actions/checkout@v4
       - uses: gaurav-nelson/[email protected]
         with:
           folder-path: "."