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
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+13-7Lines changed: 13 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,13 +6,19 @@ We welcome contributions from the community to make Buildkite CLI, `bk`, project
6
6
7
7
To get started with contributing, please follow these steps:
8
8
9
-
1. Fork the repository
10
-
2. Create a feature branch with a nice name (`git checkout -b cli-new-feature`) for your changes
11
-
3. Write your code
12
-
* We use `golangci-lint` and would be good to use the same in order to pass a PR merge. You can use `docker-compose -f .buildkite/docker-compose.yaml run golangci-lint golangci-lint run` for that.
13
-
* Make sure the tests are passing by running go test ./...
14
-
5. Commit your changes and push them to your forked repository.
15
-
7. Submit a pull request with a detailed description of your changes and linked to any relevant issues.
9
+
1. Fork the repository.
10
+
2. Create a feature branch with a nice name (`git checkout -b cli-new-feature`) for your changes.
11
+
3. Install [mise](https://mise.jdx.dev/) and run `mise install`.
12
+
4. Install the local git hooks with `mise run hooks`.
13
+
5. Write your code.
14
+
6. Run the local checks before opening a pull request.
15
+
* Format the code with `mise run format`.
16
+
* Lint with `mise run lint`.
17
+
* Make sure the tests pass with `mise run test`.
18
+
* Run `mise run generate` after GraphQL changes. If you need to refresh `schema.graphql`, set `BUILDKITE_GRAPHQL_TOKEN` first.
19
+
* If you prefer the containerized lint setup, `docker-compose -f .buildkite/docker-compose.yaml run golangci-lint golangci-lint run` still works.
20
+
7. Commit your changes and push them to your forked repository.
21
+
8. Submit a pull request with a detailed description of your changes and links to any relevant issues.
16
22
17
23
The team maintaining this codebase will review your PR and start a CI build for it. For security reasons, we don't automatically run CI against forked repos, and a human will review your PR prior to its CI running.
0 commit comments