-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Updated docs for --env-file comments handling #4642
Conversation
Signed-off-by: Saurabh Kumar <[email protected]>
This comment was marked as resolved.
This comment was marked as resolved.
Oh! Actually ignore my previous comment; looks like it's complaining about the name not matching your Git config 🤔
I can mark it to pass |
Thank you for reviewing my first PR. I'm excited to contribute to Docker, but I'm still learning the ropes. If there's anything specific I should do or consider, please let me know. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM! Thank you @desmond3th
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, thanks!
Thank you so much for merging my first PR. I look forward to making more contributions in the future. Thanks again! |
--env-file
doesn't support inline comments #4404- What I did
Updated the documentation to clarify how comments are handled when using the --env-file option.
- How I did it
Made changes in run.md file.
- Description for the changelog
Improved documentation clarity regarding --env-file comments handling.
- A picture of a cute animal (not mandatory but encouraged)