Skip to content

Conversation

MKVEERENDRA
Copy link

@MKVEERENDRA MKVEERENDRA commented Mar 7, 2025

wtclient: Add descriptions for session and terminate commands
Improved user guidance by adding detailed CLI help text for the session and terminate subcommands in the watchtower client (wtclient).

Fixed formatting issues flagged by the linter.

Fixes: #9583

Change Description
Adds helpful descriptions for lncli wtclient session and lncli wtclient terminate to make the CLI more user-friendly. No logic changes.

Steps to Test

  1. lncli wtclient
    Check that the session and terminate commands now have clear descriptions.

  2. make lint

PR Checklist
Passes all CI checks

Follows code and doc style (80 char lines, proper formatting)

Commits follow ideal structure

Not a typo-only change

No tests required (CLI help text only)

No release notes change needed

Copy link
Contributor

coderabbitai bot commented Mar 7, 2025

Important

Review skipped

Auto reviews are limited to specific labels.

🏷️ Labels to auto review (1)
  • llm-review

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.


Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@ellemouton
Copy link
Collaborator

thanks for the contribution @MKVEERENDRA ,

Please read through our contribution guidelines: Contribution Guidelines

where you will find info on: how to structure commits & how to name commits 🙏

@twofaktor
Copy link
Contributor

utACK

@MKVEERENDRA
Copy link
Author

@ellemouton ok I will do that to further PR.

@MKVEERENDRA
Copy link
Author

@dennisreimann can you pls review my PR.

@yyforyongyu
Copy link
Member

what's the difference between this and #9584?

@MKVEERENDRA
Copy link
Author

what's the difference between this and #9584?

The previous PR (#9584) was addressing the same issue, but I decided to delete it and create a new one to ensure a cleaner commit history and follow best practices.

Copy link

@Biloparoch Biloparoch left a comment

Choose a reason for hiding this comment

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

Ok

@yyforyongyu
Copy link
Member

As mentioned above and in this comment, PRs must follow the contribution guidelines.

@hieblmi hieblmi added the good first review Pull Requests that are suitable for new contributors that want to learn code review label Mar 28, 2025
@twofaktor
Copy link
Contributor

Will anyone on the team continue to follow up on this PR? Issue related #9583

@saubyk
Copy link
Collaborator

saubyk commented Apr 14, 2025

Will anyone on the team continue to follow up on this PR? Issue related #9583

Haven't seen any update after the last review comment. Ball's in @MKVEERENDRA 's court

@twofaktor
Copy link
Contributor

Will anyone on the team continue to follow up on this PR? Issue related #9583

Haven't seen any update after the last review comment. Ball's in @MKVEERENDRA 's court

If this guy never responds again, will no one from the Lightning Labs team take care of it?

@ellemouton
Copy link
Collaborator

If this guy never responds again, will no one from the Lightning Labs team take care of it?

@twofaktor - it's not a high prio issue & also is a really nice first-contribution project, so ideally would like to leave it for someone looking to make their first contribution to lnd.

@MKVEERENDRA
Copy link
Author

Hey @ellemouton @twofaktor 👋

Apologies for the delay. I'm ready to wrap this up and would love to get this PR merged. Let me know if there's anything else you'd like me to update or improve. Happy to make any recommended changes. Thanks!

Copy link
Contributor

@twofaktor twofaktor left a comment

Choose a reason for hiding this comment

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

utACK

@twofaktor
Copy link
Contributor

@ellemouton could you review this PR?

@saubyk saubyk added this to the v0.20.0 milestone Apr 15, 2025
Copy link

@AbhinavAnand241201 AbhinavAnand241201 left a comment

Choose a reason for hiding this comment

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

ACK with a small suggestion:

The changes improve the CLI help text by making descriptions clearer and more informative. The formatting is correct and the changes are focused.

One small suggestion: In the terminateSessionCommand, changing ArgsUsage: "id" to ArgsUsage: "session_id" would make it even clearer what kind of ID is expected, consistent with the improved clarity in the rest of the changes.

Overall, good improvements to the CLI documentation!

@MKVEERENDRA
Copy link
Author

Thanks! @AbhinavAnand241201 Appreciate the ACK and the helpful suggestion.

You're absolutely right — changing ArgsUsage: "id" to ArgsUsage: "session_id" makes the help text more explicit and aligned with the rest of the improvements. Just pushed that update 🙌

Let me know if you spot anything else!

Copy link

@AbhinavAnand241201 AbhinavAnand241201 left a comment

Choose a reason for hiding this comment

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

i noticed u worked on the optional improvement,... i suggested upon .. ....
everything else looks fine ..
👍🏻

@ellemouton ellemouton self-requested a review April 17, 2025 13:49
Copy link
Collaborator

@ellemouton ellemouton left a comment

Choose a reason for hiding this comment

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

@MKVEERENDRA
As requested a couple times before, please read our contribution guidelines regarding how to go about structuring commits and titling commits. Also, I think previously I made this comment on another PR but then you closed that in order to open this one. Rather just push changes to this PR instead of opening a new on. The changes in this PR can really all just be in a single commit.

… fixes.

- Added detailed descriptions for the session and terminate commands in wtclient to improve user guidance and clarity.
- Changed the ArgsUsage for the session command from 'id' to 'session_id'.
- Refined descriptions to explain the purpose of each command.
- Fixed long description lines to adhere to the 80-character line limit.
- Updated the release notes for version 0.19.0.

Fixes: lightningnetwork#9583
@MKVEERENDRA
Copy link
Author

@yyforyongyu Why was the PR closed without merging? There were unmerged commits — should we reopen it or create a new one?

@MKVEERENDRA
Copy link
Author

@saubyk can you reopen it or please clarify that like why it was closed.

@ellemouton ellemouton reopened this Apr 25, 2025
@ellemouton
Copy link
Collaborator

@MKVEERENDRA - i've reopened it

@ellemouton
Copy link
Collaborator

@MKVEERENDRA - note that commit message structure has still not been followed here. please read our guidelines carefully

@MKVEERENDRA
Copy link
Author

@ellemouton "note that commit message structure has still not been followed here. please read our guidelines carefully" -- Can you pls elaborate that what I not been followed, I am bit confused like I read the guidelines carefully and did many changes like detail commit messages and strink commit ..etc, but I did not find any difference like what is wrong.
Further details help me alot.

@MKVEERENDRA MKVEERENDRA requested a review from ellemouton April 30, 2025 04:09
@ellemouton
Copy link
Collaborator

@MKVEERENDRA - see here

@lightninglabs-deploy
Copy link

@ellemouton: review reminder

Copy link
Collaborator

@ellemouton ellemouton left a comment

Choose a reason for hiding this comment

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

please re-request once updated

@twofaktor
Copy link
Contributor

please re-request once updated

It is being worked on in parallel PR #9765 which seems more appropriate

@saubyk
Copy link
Collaborator

saubyk commented May 12, 2025

It is being worked on in parallel PR #9765 which seems more appropriate

In that case, can we close this pr now?

@MKVEERENDRA
Copy link
Author

Alright, if PR #9765 is more appropriate, let's go ahead and close this one.

The reason I initially opened this PR was to contribute the changes quickly, but since it's now being handled better in parallel, I'm happy to close it here.

Also, @ellemouton — you mentioned "commit message structure has still not been followed." I did read the contribution guidelines carefully and tried to apply them (added detailed messages, squashed commits, etc.), so I’m not exactly sure what I missed.

Could you please help clarify what specifically was incorrect? That would help me a lot to improve in the future.

Thanks!

@saubyk saubyk closed this May 13, 2025
@ellemouton
Copy link
Collaborator

ellemouton commented May 13, 2025

@MKVEERENDRA - did you see the link I posted above? this one?

basically you need to have a short (max 50 char title) that starts with the package being touched in that commit and then you can follow it with a description body that wraps at 80.

So a title for this commit could have been: cmd/commands: add descriptions to tower commands

@MKVEERENDRA
Copy link
Author

@ellemouton Ohh now I get it, Tq for the information.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

good first review Pull Requests that are suitable for new contributors that want to learn code review

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[bug]: missing description to wtclient command "session" and "terminate" command option

9 participants