zellij/CONTRIBUTING.md

Contributing to Zellij

Thanks for considering contributing to Zellij!

First: if you're unsure of anything, feel free to ask on our Discord server. We're a friendly and welcoming bunch!

Code of Conduct

Before contributing please read our Code of Conduct which all contributors are expected to adhere to.

Building

To build Zellij, we're using cargo-make – you can install it by running cargo install --force cargo-make.

To edit our manpage, the mandown crate (cargo install mandown) is used and the work is done on a markdown file in docs/MANPAGE.md.

Here are some of the commands currently supported by the build system:

# Format code, build, then run tests and clippy
cargo make
# You can also perform these actions individually
cargo make format
cargo make build
cargo make test
# Run Zellij (optionally with additional arguments)
cargo make run
cargo make run -l strider
# Run Clippy (potentially with additional options)
cargo make clippy
cargo make clippy -W clippy::pedantic
# Install Zellij to some directory
cargo make install /path/of/zellij/binary
# Publish the zellij and zellij-tile crates
cargo make publish
# Update manpage
cargo make manpage

To run install or publish, you'll need the package binaryen in the version wasm-opt --version > 97, for it's command wasm-opt.

To run test, you will need the package pkg-config and a version of openssl.

Running the end-to-end tests

Zellij includes some end-to-end tests which test the whole application as a black-box from the outside. These tests work by running a docker container which contains the Zellij binary, connecting to it via ssh, sending some commands and comparing the output received against predefined snapshots.

Should you be a macOS (including m1) user, please follow these commands before. (expand here):

1. rustup target add x86_64-unknown-linux-musl
2. brew install messense/macos-cross-toolchains/x86_64-unknown-linux-musl
3. export CC_x86_64_unknown_linux_musl=$(brew --prefix)/bin/x86_64-unknown-linux-musl-gcc
4. export AR_x86_64_unknown_linux_musl=$(brew --prefix)/bin/x86_64-unknown-linux-musl-ar
5. export CARGO_TARGET_X86_64_UNKNOWN_LINUX_MUSL_LINKER=$CC_x86_64_unknown_linux_musl

To run these tests locally, you'll need to have both docker and docker-compose installed. Once you do, in the repository root:

1. docker-compose up -d will start up the docker container
2. cargo make build-e2e will build the generic linux executable of Zellij in the target folder, which is shared with the container
3. cargo make e2e-test will run the tests

To re-run the tests after you've changed something in the code base, be sure to repeat steps 2 and 3.

How we treat clippy lints

We currently use clippy in GitHub Actions with the default settings that report only clippy::correctness as errors and other lints as warnings because Zellij is still unstable. This means that all warnings can be ignored depending on the situation at that time, even though they are also helpful to keep the code quality. Since we just cannot afford to manage them, we are always welcome to fix them!

Here is the detailed discussion if you want to see it.

Looking for something to work on?

If you are new contributor to Zellij going through beginners should be a good start or you can join our public Discord server, we would be happy to help finding something interesting to work on and guide through.

Filing Issues

Bugs and enhancement suggestions are tracked as GitHub issues.

Lacking API for plugin in Zellij?

If you have a plugin idea, but Zellij still doesn't have API required to make the plugin consider opening an issue and describing your requirements.

How Do I Submit A (Good) Bug Report?

After you've determined which repository your bug is related to and that the issue is still present in the latest version of the master branch, create an issue on that repository and provide the following information:

• Use a clear and descriptive title for the issue to identify the problem.
• Explain which behavior you expected to see instead and why.
• Describe the exact steps to reproduce the problem in as many details as necessary.
• When providing code samples, please use code blocks.

How Do I Submit A (Good) Enhancement Suggestion?

Instructions are similar to those for bug reports. Please provide the following information:

• Use a clear and descriptive title for the issue to identify the suggestion.
• Provide a description of the suggested enhancement in as many details as necessary.
• When providing code samples, please use code blocks.

Submitting Pull Requests

Instructions are similar to those for bug reports. Please provide the following information:

• If this is not a trivial fix, consider creating an issue to discuss first and later link to it from the PR.
• Use a clear and descriptive title for the pull request.
  • Follow Conventional Commit specification where sufficiently large or impactful change is made.
• Provide a description of the changes in as many details as necessary.

Before submitting your pull request, also make sure that the following conditions are met:

• Your new code adheres to the code style through running cargo fmt.
• Your new code passes all existing and new tests through running cargo test.