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

Add pueue status query documentation #438

Merged
merged 5 commits into from
May 23, 2023

Conversation

fluffysquirrels
Copy link

@fluffysquirrels fluffysquirrels commented May 21, 2023

I added a description of the query syntax to the pueue status command.

A detailed description will show if you use pueue status --help.

pueue status -h (short help in clap) shows a hint to use --help to see the full description.

Checklist

  • I picked the correct source and target branch.
  • I included a new entry to the CHANGELOG.md.
  • I checked cargo clippy and cargo fmt. The CI will fail otherwise anyway.
  • Not applicable: I added tests for this feature or adjusted existing tests.
  • Not applicable: I checked if anything in the wiki needs to be changed.

@fluffysquirrels fluffysquirrels marked this pull request as ready for review May 21, 2023 11:26
@fluffysquirrels fluffysquirrels changed the title Add pueue status query documentation Add pueue status query documentation May 21, 2023
@Nukesor
Copy link
Owner

Nukesor commented May 23, 2023

Nice :)

Thanks a lot for writing this! I completely forgot that this is on my todo list 😅

@github-actions
Copy link

Test Results

    3 files  ±0    22 suites  ±0   2m 7s ⏱️ +4s
126 tests ±0  126 ✔️ ±0  0 💤 ±0  0 ±0 
272 runs  ±0  272 ✔️ ±0  0 💤 ±0  0 ±0 

Results for commit 600400e. ± Comparison against base commit facfb2b.

@Nukesor Nukesor merged commit b2a9af9 into Nukesor:main May 23, 2023
@fluffysquirrels fluffysquirrels deleted the status-query-docs branch May 23, 2023 20:52
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