You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- Add golangci-lint configuration with core linters (errcheck, govet, staticcheck, unused), and formatters (gci, gofmt, goimports, golines) with 120 char line limit.
- Add detailed golangci-lint instructions to CONTRIBUTING.md
- Add Requirements section with gofumpt and golangci-lint links
- Update GitHub Actions to use golangci-lint v2.3.0
- Separate linting and testing steps in contribution workflow
- Apply fixes from linting
- Standarize on camelCase for JSON properties (breaking change!)
- Added exceptions for upstream JSON data
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+26-8Lines changed: 26 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,26 +15,44 @@ We encourage contributions via GitHub pull requests. Before you start, please re
15
15
***Features:** Please use our [Feature Request template](.github/ISSUE_TEMPLATE/feature_request.yaml) to describe the problem your idea solves and your proposed solution.
16
16
***Search First:** Before creating a new issue, please search existing issues to see if your topic has already been discussed.
1. **Create a new branch**for your changes based on the `main` branch.
31
+
3. **Create a new branch**for your changes based on the `main` branch.
27
32
```bash
28
33
git checkout main
29
34
git pull origin main
30
35
git checkout -b your-feature-or-bugfix-branch
31
36
```
32
-
1. **Make your changes.**
33
-
1. **Format and Lint:** Ensure your code is formatted using [gofumpt](https://github.com/mvdan/gofumpt) and [golangci-lint run ./...](https://golangci-lint.run/welcome/install/).
34
-
1. **Add Unit Tests:** All new features and bug fixes should be accompanied by relevant unit tests.
35
-
1. **Commit your changes** with a clear and descriptive message.
36
-
1. **Push your branch** to your forked repository.
37
-
1. **Open a Pull Request** from your branch to the `main` branch of the upstream `mozilla-ai/mcpd` repository,
37
+
4. **Make your changes:** You can build your changes with:
38
+
```bash
39
+
make build
40
+
```
41
+
5. **Format and Lint:** Ensure your code passes linting and formatting checks:
42
+
```bash
43
+
# Run golangci-lint (uses .golangci.yaml config)
44
+
golangci-lint run
45
+
46
+
# Auto-fix formatting issues (recommended)
47
+
golangci-lint run --fix
48
+
```
49
+
6. **Add Unit Tests:** All new features and bug fixes should be accompanied by relevant unit tests. Run tests with:
50
+
```bash
51
+
make test
52
+
```
53
+
7. **Commit your changes** with a clear and descriptive message.
54
+
8. **Push your branch** to your forked repository.
55
+
9. **Open a Pull Request** from your branch to the `main` branch of the upstream `mozilla-ai/mcpd` repository,
38
56
reference the relevant GitHub issue in your PR summary.
0 commit comments