up

.github/ISSUE_TEMPLATE/bug_report.md

@@ -8,12 +8,14 @@ assignees: ''
 ---
 
 **Describe the bug**
-A clear and concise description of what the bug is.
+<!-- Add a clear and concise description of what the bug is. -->
 
 **To Reproduce**
-Steps to reproduce the behavior:
+<!-- Steps to reproduce the behavior: -->
 
 **Expected behavior**
-A clear and concise description of what you expected to happen.
+<!-- Add a clear and concise description of what you expected to happen. -->
 
 **Additional context**
+<!-- You can include any relevant stack traces or debugging output in this section. -->
+

.github/ISSUE_TEMPLATE/feature_request.md

@@ -8,13 +8,14 @@ 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 what the problem is. For example, “I'm always frustrated when [...]”. -->
 
 **Describe the solution you'd like**
-A clear and concise description of what you want to happen.
+<!-- Describe what you want to happen. -->
 
 **Describe alternatives you've considered**
-A clear and concise description of any alternative solutions or features you've considered.
+<!-- Describe any alternative solutions or features you've considered. -->
 
 **Additional context**
-Add any other context or screenshots about the feature request here.
+<!-- Add any other context or screenshots about the feature request in this section. -->
+

.github/workflows/ci.yml

@@ -0,0 +1,62 @@
+name: CI
+
+on:
+  push:
+    branches:
+      - master
+  pull_request:
+
+env:
+  go_version: 1.21
+  GO111MODULE: on
+
+jobs:
+  Check-License:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v3
+        with:
+          version: latest
+      - uses: actions/setup-go@v3
+        with:
+          go-version: ${{ env.go_version }}
+      - run: make go-deps
+      - run: make check-license
+
+  Check-Spelling:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v3
+        with:
+          version: latest
+      - uses: actions/setup-go@v3
+        with:
+          go-version: ${{ env.go_version }}
+      - run: make go-deps
+      - run: make spellcheck
+
+  Check-Gen:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v3
+        with:
+          version: latest
+      - run: make node-deps
+      - run: make check-gen
+
+  Check-Valid:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v3
+        with:
+          version: latest
+      - run: make node-deps
+      - run: make check-valid
+
+  Salus:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v3
+        with:
+          version: latest
+      - run: make salus

CONTRIBUTING.md

@@ -1,53 +1,85 @@
-# Contributing to Rosetta-Specifications
+# Contributing to Mesh-Specifications
 
 ## Code of Conduct
 
-All interactions with this project follow our [Code of Conduct][code-of-conduct].
-By participating, you are expected to honor this code. Violators can be banned
-from further participation in this project, or potentially all Coinbase projects.
+All interactions with this project follow our [Code of Conduct](https://github.com/coinbase/code-of-conduct). By participating, you are expected to honor this code. Violators can be banned from further participation in this project, or potentially all Coinbase projects.
 
-[code-of-conduct]: https://github.com/coinbase/code-of-conduct
+## How to Contribute
 
-## Bug Reports
+You can contribute to this repository by asking questions, providing feedback, and reporting issues.
 
-* Ensure your issue [has not already been reported][1]. It may already be fixed!
-* Include the steps you carried out to produce the problem.
-* Include the behavior you observed along with the behavior you expected, and
-  why you expected it.
-* Include any relevant stack traces or debugging output.
+### Asking Questions
 
-## Feature Requests
+Submit your questions via the [Mesh Community boards][13].
 
-We welcome feedback with or without pull requests. If you have an idea for how
-to improve the project, great! All we ask is that you take the time to write a
-clear and concise explanation of what need you are trying to solve. If you have
-thoughts on _how_ it can be solved, include those too!
+### Providing Feedback
+
+You can also use the [Mesh Community boards][13] to provide feedback.
+
+### Reporting Issues
+
+You can report issues by submitting bug reports, feature requests, or pull requests via GitHub. You **must** submit [security issues](#security-issues) and [support requests](#support-requests) through the links provided.
+
+#### Bug Reports
+
+Before filing a bug report, ensure that your issue [has not already been reported][1]. It may already be fixed!
+
+If your bug hasn’t been fixed, follow these steps to file a bug report:
+
+1. [Open an issue in GitHub][10].
+2. Add a title for your bug report. It should briefly describe the problem.
+3. Follow the template that appears in the Write text box. This is the best way to describe the bug.
+4. Click _Submit new issue_ to finish filing the bug report.
+
+#### Feature Requests
+
+We welcome feedback with or without pull requests. If you have an idea for how to improve the project, great! All we ask is that you take the time to write a clear and concise explanation of the need you are trying to solve. If you have thoughts on _how_ it can be solved, include those too!
+
+To submit a feature request, follow these steps:
+
+1. [Open an issue in GitHub][10].
+2. Add a title for your feature request. It should briefly describe your requested feature.
+3. Follow the template that appears in the Write text box. This is the best way to explain your request. Be clear and concise in your responses.
+4. Click _Submit new issue_ to submit the feature request.
 
 The best way to see a feature added, however, is to submit a pull request.
 
-## Pull Requests
+#### Pull Requests
+
+Before creating your pull request, it's usually worth asking whether the code you're planning on writing will be considered for merging. You can do this by [opening an issue][1] and asking. It may also help give the maintainers context for when the time comes to review your code.
 
-* Before creating your pull request, it's usually worth asking if the code
-  you're planning on writing will actually be considered for merging. You can
-  do this by [opening an issue][1] and asking. It may also help give the
-  maintainers context for when the time comes to review your code.
+Ensure that your [commit messages are well-written][2]. This can double as your pull request message, so it pays to take the time to write a clear message.
 
-* Ensure your [commit messages are well-written][2]. This can double as your
-  pull request message, so it pays to take the time to write a clear message.
+To submit your pull request, follow these steps:
 
-* Add tests for your feature. You should be able to look at other tests for
-  examples. If you're unsure, don't hesitate to [open an issue][1] and ask!
+1. Follow these instructions on how to [open a pull request in GitHub][11].
+2. Click _Create pull request_ to submit your pull request.
 
-* Submit your pull request!
+Once you submit your pull request, a reviewer will revise it, and either approve it or offer suggestions.
 
-## Support Requests
+#### Security Issues
 
-For security reasons, any communication referencing support tickets for Coinbase
-products will be ignored. The request will have its content redacted and will
-be locked to prevent further discussion.
+You can send a report through Coinbase's [H1 program][12]. Check out the [Security][14] tab for more information.
+
+#### Support Requests
 
 All support requests must be made via [our support team][3].
 
-[1]: https://github.com/coinbase/rosetta-specifications/issues
-[2]: https://medium.com/brigade-engineering/the-secrets-to-great-commit-messages-106fc0a92a25
+**For security reasons, any communication referencing support tickets for Coinbase products will be ignored.** The request will have its content redacted and will be locked to prevent further discussion.
+
+© 2022 Coinbase
+
+<!-- Before adding link 15, populate link 4. One you do that, please erase this note. --->
+[1]: https://github.com/coinbase/mesh-specifications/issues
+[2]: https://chris.beams.io/posts/git-commit/#seven-rules
 [3]: https://support.coinbase.com/customer/en/portal/articles/2288496-how-can-i-contact-coinbase-support-
+<!--- [4]: link removed --->
+[5]: https://github.com/coinbase/mesh-specifications/issues/new/choose
+[6]: https://github.com/coinbase/mesh-specifications/issues/new?assignees=&labels=bug&template=bug_report.md&title=
+[7]: https://github.com/coinbase/mesh-specifications/issues/new?assignees=&labels=enhancement&template=feature_request.md&title=
+[8]: https://github.com/coinbase/mesh-specifications/pulls
+[9]: https://github.com/coinbase/mesh-specifications/compare
+[10]: https://docs.github.com/en/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/creating-an-issue-or-pull-request#creating-an-issue
+[11]: https://docs.github.com/en/desktop/contributing-and-collaborating-using-github-desktop/working-with-your-remote-repository-on-github-or-github-enterprise/creating-an-issue-or-pull-request#creating-a-pull-request
+[12]: https://hackerone.com/coinbase
+[13]: https://github.com/coinbase/mesh-specifications/security

Makefile

@@ -1,5 +1,6 @@
-.PHONY: node-deps go-deps deps gen check-gen add-license check-license spellcheck shellcheck salus
-LICENCE_SCRIPT=addlicense -c "Coinbase, Inc." -l "apache" -v
+.PHONY: node-deps go-deps deps gen check-gen add-license check-license spellcheck shellcheck salus check-valid
+ADDLICENSE_IGNORE=-ignore ".github/**/*" -ignore ".idea/**/*"
+LICENCE_SCRIPT=addlicense -c "Coinbase, Inc." -l "apache" -v ${ADDLICENSE_IGNORE}
 GO_INSTALL=GO111MODULE=off go get
 
 node-deps:
@@ -14,6 +15,9 @@ deps: node-deps go-deps
 gen:
 	./codegen.sh;
 
+check-valid:
+	swagger-cli validate api.yaml
+
 check-gen: | gen
 	git diff --exit-code
 
@@ -32,4 +36,4 @@ shellcheck:
 salus:
 	docker run --rm -t -v ${PWD}:/home/repo coinbase/salus
 
-release: shellcheck spellcheck check-gen check-license salus
+release: check-valid shellcheck spellcheck check-gen check-license salus