-
Notifications
You must be signed in to change notification settings - Fork 334
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 margins between items in output area scrolling list #993
Comments
Seems like a great opportunity for your first PR! You seem really close to having the knowledge you are referring to. I would help walk you through what to do if you are interested. |
Hi BenRussert, I will really appreciate the help! Now I managed to do |
You are getting close. What you will need to do next is fork the hydrogen repo (there is a button up top on github to do this). This will make your own copy of the repo. Next you will need to add a remote which leads to your fork. Commit your changes (I recommend doing this on a new branch) and push the branch to your newly added fork. I know this sounds complicated, but i promise nobody knows how to do this until they do and it will be easier next time. For example my fork is at
Now just go back to your fork on github in your browser (https://github.com/benrussert/hydrogen in my case) and you will see a message that says something along the lines of "this was changed recently" and a button that says "new pull request". |
Thank you so much for the detailed instructions. Will give it a try later today! |
Hi,
Currently, in the scrolling list view of the output area, the output items are too close to each other and look not so good.
It will be nice if a small margin is added between the output items. It can be done by modifying hydrogen.less:
.output-area{ div { margin-bottom: 10px; } }
I know I should probably submit a pull request but I am still very new to github and so not sure how to do so. Hope someone with the knowledge can help incorporate the change. Thank you so much!
The text was updated successfully, but these errors were encountered: