-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Improve view of /notes page #4937
Comments
This issue is for @AnthoniaOkafor. Thanks! |
Thanks! |
@gauravano Can I work on this issue? |
Hey @shreyateeza, this issue was created for @AnthoniaOkafor as they were searching for their first-issue with us. I can create one for you too if you are looking for a |
@gauravano Thanks! Yes, I want to solve a more |
@gauravano please create similar issue to for me. |
hey @shreyateeza @EngrEric, added your name to the list -#4963. Will ping you shortly with a issue. Thanks! |
@gauravano You have added my name in it. Please assign me an issue to work on. |
hey @shreyateeza sorry for the delay. I have created one for you at #4979 . Thanks! |
@gauravano please look into gitter chat. |
@gauravano please i am waiting for my own too |
@gauravano Please can i have one to work on too. |
@AnthoniaOkafor Hi, just checking if you've gotten stuck on this at all, or if I could help in any way? Thanks! We are starting to request that contributors show some sort of activity towards a first-timers-only issue after claiming it within a week because there is high demand for them. (whether that is asking for more time, help, opening a PR, etc.) |
Hello @sashadev-sky. I'll open a PR today. Thanks |
Hi @sashadev-sky. I have successfully resolved my FTO issue and pushed it to my fork. However I already opened a PR last week. Do I open a new PR or continue with my first PR? #4961 (comment) |
@AnthoniaOkafor, congrats on opening your PR. |
Hey @EngrEric, thanks. My laptop runs on Windows but I run the app on Cloud9. If you are finding it challenging running it locally, you could try Cloud9. |
Also @EngrEric , I remember you mentioned about the mysql error in gitter channel . If you are still having that same issue then you can update your local master branch by After that, you can update your feature-branch i.e., branch on which you have worked on using If you haven't made any feature-branch till now, you can do that by:(Do this after updating local master branch only otherwise you have to rebase the branch formed in this step)
|
Ok @gauravano, I'll do just that. Many thanks |
@AnthoniaOkafor if the changes you make are still relevant to the first PR you opened then continue pushing them there. All you have to do is add the changes to that branch and push it Otherwise you create a new branch for a different feature or something addressing a different issue and push that up. Work on one branch will not effect work on the other and your local repo will update to reflect which branch you are on. |
@AnthoniaOkafor I think @gauravano has been following your original PR closer so he can confirm but it looks like he wants you to push your changes there His comments above were to help resolve @EngrEric's question |
@AnthoniaOkafor check here - #4961 (comment) |
@gauravano thanks for bearing my disturbances i got it working now. |
Hi, this is a first-timers-only issue. This means we've worked to make it more legible to folks who either haven't contributed to our codebase before, or even folks who haven't contributed to open source before.
If that's you, we're interested in helping you take the first step and can answer questions and help you out as you do. Note that we're especially interested in contributions from people from groups underrepresented in free and open source software!
We know that the process of creating a pull request is the biggest barrier for new contributors. This issue is for you 💝
If you have contributed before, consider leaving this one for someone new, and looking through our general help wanted issues. Thanks!
🤔 What you will need to know.
Nothing. This issue is meant to welcome you to Open Source :) We are happy to walk you through the process.
📋 Step by Step
🙋 Claim this issue: Comment below. If someone else has claimed it, ask if they've opened a pull request already and if they're stuck -- maybe you can help them solve a problem or move it along!
📝 Update:
![notes_view](https://user-images.githubusercontent.com/20878070/53973220-5f99fa00-4126-11e9-8e7a-af759b5f0eb2.png)
At https://publiclab.org/notes the Spam and Read more buttons are rendering on the different lines as visible in the screen shot
Update https://github.com/publiclab/plots2/blob/master/app/views/notes/_notes.html.erb#L49-L52 so as to show both buttons in a single line enhancing the page design
After changing the view, also attach the screenshot of updated view in the PR.
💾 Commit your changes
🔀 Start a Pull Request. There are two ways how you can start a pull request:
If you are familiar with the terminal or would like to learn it, here is a great tutorial on how to send a pull request using the terminal.
You can also edit files directly in your browser and open a pull request from there.
🤔❓ Questions?
Leave a comment below!
Is someone else already working on this?
We encourage you to link to this issue by mentioning the issue # in your pull request, so we can see if someone's already started on it. If someone seem stuck, offer them some help! Otherwise, take a look at some other issues you can help with. Thanks!
The text was updated successfully, but these errors were encountered: