Improve development environment documentation to explain first steps like setting up a SSH key, forking, cloning the fork, etc.
@janyu99 pointed this out in #100 when setting up the development environment. For beginners, it's not an obvious first step since most people getting started with the Fedora community have not worked with Pagure before. It would be helpful to point out some of these steps for the benefit of first-timers.
If something is already written in the Pagure usage docs, it shouldn't be written twice (e.g. the pull requests docs page). In our docs, we could point to the Pagure docs as a reference where needed.
Otherwise, we can write new docs on our own where needed.
Metadata Update from @jflory7: - Issue assigned to janyu99
@janyu99 I opened this from your comment in #100. Feel free to work on this as a first contribution! :thumbsup:
@jflory7 Great! I'll start working on this immediately :pencil:
@jflory7 I noticed that the setup instructions were updated with the 'fork and clone' step, so I just added one more step to the instructions to tie it all together :thumbsup: Here is my pull request: https://pagure.io/fedora-commops/fedora-happiness-packets/pull-request/142
@janyu99 Thanks, this PR did the trick. I'm going to close this ticket as complete! Thanks for working on this. :clapper:
Metadata Update from @jflory7: - Issue close_status updated to: complete - Issue status updated to: Closed (was: Open)
Metadata Update from @jflory7: - Issue set to the milestone: Summer Coding 2019: community bonding
Metadata Update from @janyu99: - Assignee reset
Login to comment on this ticket.