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
stale-issue-message: "This issue is stale because it has been open for ${{ env.PR_DAYS_BEFORE_STALE }} days with no activity. Leave a comment to avoid closing this issue in ${{ env.PR_DAYS_BEFORE_CLOSE }} days."
23
+
close-issue-message: "This issue was closed because it has been inactive for ${{ env.PR_DAYS_BEFORE_CLOSE }} days since being marked as stale."
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+22-10Lines changed: 22 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,24 +10,36 @@ Contributions to this project are [released](https://help.github.com/articles/gi
10
10
11
11
Please note that this project is released with a [Contributor Code of Conduct](CODE_OF_CONDUCT.md). By participating in this project you agree to abide by its terms.
12
12
13
+
## What we're looking for
14
+
15
+
We can't guarantee that every tool, feature, or pull request will be approved or merged. Our focus is on supporting high-quality, high-impact capabilities that advance agentic workflows and deliver clear value to developers.
16
+
17
+
To increase the chances your request is accepted:
18
+
* Include real use cases or examples that demonstrate practical value
19
+
* If your request stalls, you can open a Discussion post and link to your issue or PR
20
+
* We actively revisit requests that gain strong community engagement (👍s, comments, or evidence of real-world use)
21
+
22
+
Thanks for contributing and for helping us build toolsets that are truly valuable!
23
+
13
24
## Prerequisites for running and testing code
14
25
15
26
These are one time installations required to be able to test your changes locally as part of the pull request (PR) submission process.
16
27
17
-
1.install Go [through download](https://go.dev/doc/install) | [through Homebrew](https://formulae.brew.sh/formula/go)
> **Important**: Please open your pull request against the `next` branch, not `main`. The `next` branch is where we integrate new features and changes before they are merged to `main`.
23
-
24
33
1.[Fork][fork] and clone the repository
25
-
1. Make sure the tests pass on your machine: `go test -v ./...`
26
-
1. Make sure linter passes on your machine: `golangci-lint run`
27
-
1. Create a new branch: `git checkout -b my-branch-name`
28
-
1. Make your change, add tests, and make sure the tests and linter still pass
29
-
1. Push to your fork and [submit a pull request][pr] targeting the `next` branch
30
-
1. Pat yourself on the back and wait for your pull request to be reviewed and merged.
34
+
2. Make sure the tests pass on your machine: `go test -v ./...`
35
+
3. Make sure linter passes on your machine: `golangci-lint run`
36
+
4. Create a new branch: `git checkout -b my-branch-name`
37
+
5. Add your changes and tests, and make sure the Action workflows still pass
38
+
- Run linter: `script/lint`
39
+
- Update snapshots and run tests: `UPDATE_TOOLSNAPS=true go test ./...`
0 commit comments