Skip to content
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

docs: include README section on locking stuff #842

Merged
merged 3 commits into from
Dec 2, 2024

Conversation

EthanFreestone
Copy link
Contributor

No description provided.

@EthanFreestone EthanFreestone marked this pull request as draft December 2, 2024 15:21
Copy link

github-actions bot commented Dec 2, 2024

License CLA Stuck? (Developer should make sure that it is really stuck before clicking)

Copy link

github-actions bot commented Dec 2, 2024

Test Results

142 tests  ±0   138 ✅ ±0   5m 36s ⏱️ +3s
 17 suites ±0     4 💤 ±0 
 17 files   ±0     0 ❌ ±0 

Results for commit 188971c. ± Comparison against base commit 35cc60a.

♻️ This comment has been updated with latest results.

README.md Show resolved Hide resolved
README.md Outdated Show resolved Hide resolved
Copy link
Contributor

@ostephens ostephens left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@EthanFreestone EthanFreestone marked this pull request as ready for review December 2, 2024 17:01
@EthanFreestone EthanFreestone merged commit 62531da into master Dec 2, 2024
11 checks passed
@EthanFreestone EthanFreestone deleted the docks/lock_readme branch December 2, 2024 17:02
Jack-Golding pushed a commit that referenced this pull request Dec 6, 2024
* docs: include README section on locking stuff

* docks: intsallation overview and slight addition to lock specific wording

* docs: added CPU specific wording with link to example module requirements wiki page
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants