Skip to content

docs: be clear about branch of CLEO to use #32

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
yoctoyotta1024 merged 1 commit into from
Apr 11, 2025
Merged

docs: be clear about branch of CLEO to use #32

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
3 changes: 2 additions & 1 deletion docs/source/usage/getstart.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -27,10 +27,11 @@ which will be used when you try to commit something or you execute ``pre-commit
more about the powers of pre-commit from `their documentation <https://pre-commit.com>`_.

For now, CLEO's python packages are not readily installable and so you will have to clone the CLEO
repository to somewhere in your filesystem:
repository to somewhere in your filesystem and checkout to the performance_testing_cleo branch:
.. code-block:: console

$ git clone https://github.com/yoctoyotta1024/CLEO.git
$ cd CLEO && git switch performance_testing_cleo


That's it, you're done! Now maybe you want to compile and run one of the setups in ``src/``.
Expand Down
Loading