-
Notifications
You must be signed in to change notification settings - Fork 132
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.
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
Improvements to CONTRIBUTING doc #2611
Conversation
@@ -10,7 +10,8 @@ Install these dependencies: | |||
|
|||
1. [Node](https://nodejs.org/en/download/package-manager/) - the version specified in the `.node-version` file at the root folder. | |||
2. [Yarn](https://yarnpkg.com/) - a package manager for installing dependencies and starting Brim in dev mode. | |||
3. [Go](https://go.dev/doc/install) - to compile some Zed dependencies. | |||
3. [Go](https://go.dev/doc/install) - to compile some [Zed](https://zed.brimdata.io/) dependencies. | |||
4. Typical command line tools, such as `make`, `unzip`, and `curl` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I called these out because I found that on a minimal install of Ubuntu or Windows, some of these tools were not present. The debug logs generated when the yarn
commands fail are fairly clear in explaining what's missing, but I figure if we mention these up front it might save the reader some debug cycles.
"release": "electron-builder --mac", | ||
"release": "electron-builder --publish never", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In addition to dropping the --mac
so it builds for the detected OS, the --publish never
prevents it from seeking out a GitHub token env var to publish with and failing when it's not found. Our Actions Workflows generally handle the job for the GitHub-published ones.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is great. Thanks Phil.
Community issue #2569 led me to revisit our user-facing docs for creating release artifacts. I thought they might be in some ways confusing or incomplete when viewed by an outsider. Specifically, the
yarn release
that was referenced previously was wired up to run on MacOS, which may have suited our internal needs but might confuse a user such as the one in #2569 running on a non-Mac OS. Since Electron Builder defaults to building for the detected OS, I've changed it over to that.We also only had code signing details for MacOS (and the ones we had needed a little adjustment), so I've included the ones for Windows as well.
I fixed a couple typos, fixed some links, and improved some other wording while I was in there.
I'll add PR comments to further point out a couple specific changes.