-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
populate SUPPORTED_COMMANDS cli #2157
base: main
Are you sure you want to change the base?
Conversation
Thanks for contributing. I would suggest a simpler approach. Just modify Lines 130 to 142 in 78249d9
into def main():
command_name = sys.argv[1]
if command_name == "chat":
chat()
elif command_name == "env":
print_env()
else:
train(command_name) It should be enough, what do you think? |
Thanks for the feedback! I see your point about simplifying the approach. My initial thought was to keep the existing structure to maintain clarity for users regarding supported commands. I mean it could be done in that straight forward way but as a user I would not know what commands I could use. To find out I'd actually have to dig into the code and see what's gonna be executed e.g. how Maybe I am overcomplicating things here. This is my first contribution so I don't know what kinda users (weather technical enough or not) are using Either way, I will adjust the implementation based on what you think is best! |
As a user I'd use
We're currently tweaking |
@lewtun anything to say here maybe? You opened the issue and might have some additional suggestion.
Either way, I am happy to go with your suggestion. Please let me know how you'd want it. |
In the future, we will probably move to subparser for the trl cli, so
Do you mind trying with the above suggestion? Also, the critical point here is to add the tests: like this one Lines 20 to 28 in 78249d9
|
Hi, do you want me to add a test for each model or some dynamic way? So if I understand correctly, you want to use the test you just proposed and this approach:
? |
For each model. The args may vary a lot so I don't think it's possible to have a generic test for all scripts
That's right |
What does this PR do?
This closed #2101
Fixes # (issue)
Before submitting
Pull Request section?
to it if that's the case.
documentation guidelines.
Who can review?
@lewtun
Anyone in the community is free to review the PR once the tests have passed. Feel free to tag
members/contributors who may be interested in your PR.