Skip to content

Fix script name and command in contribution guide #10047

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Oct 10, 2025
Merged

Fix script name and command in contribution guide #10047

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions CONTRIBUTING.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -101,10 +101,10 @@ Cube.is written in a mixture of JavaScript, TypeScript, and Rust. TypeScript and
11. Run `yarn link @cubejs-backend/server-core` in your project directory.
12. Run `yarn dev` to start your testing project and verify changes.

Instead of running all of the above commands manually you can use the `dev_env_setup.sh` script:
Instead of running all of the above commands manually you can use the `dev-env.sh` script:

1. Clone the Cube repository, `git clone https://github.com/cube-js/cube`.
2. Navigate to your working projects directory and run `/path/to/cube/repo/dev_env_setup.sh`. The script will
2. Navigate to your working projects directory and run `/path/to/cube/repo//dev-env.sh setup`. The script will
ask you some questions and run all the required commands. In case you decide to create a new testing project,
it will be created in the current directory (that is why you probably don't want to run this script within
cube repo directory).
Expand Down