Handle an OpenMRS Ticket (Activity)

Title	Handle an OpenMRS Ticket
Overview	Use git and Eclipse to handle an OpenMRS ticket.
Prerequisites	A working github account, Eclipse configured for OpenMRS
Learning Objectives	After successfully completing this activity, the learner should be able to: fork, clone, checkout, and commit code using git and github. follow the process defined by OpenMRS for tickets.
Process Skills Practiced

Video

Watch the OpenMRS University video, http://www.youtube.com/watch?v=SbbDvMVgRWo entitled, “OpenMRS University: Contributing Code.”

Handle a Ticket

The following steps are followed in the video:

1. Claim the ticket
2. Fork the appropriate repository on github.
   • The project name is in the upper-left corner of the ticket next to the ticket id.
3. Clone the repository to your local machine.

   git clone <repository url>

   • The repository url should point to the forked copy on your github account.
4. Set the upstream repository

   git remote add upstream <repository url>

   • The repository url should point to the original copy of the project on github.
   • You must be in the project directory for this command to succeed.
5. Fetch all the current branches of the project.

   git fetch –all

   • FIXME I don’t quite understand why this is necessary. What did we have after the clone?
6. Pull all changes from the upstream master

   git pull –rebase upstream master

   • FIXME In the video and on my sample ticket, there were no changes. I don’t understand how there could be after the fetch (much less after the clone).
7. Create a branch to work in

   git checkout -b <branch name>

   • Use the ticket identifier as the branch name.
8. Import the project into Eclipse
   • Use the “Browse..” button to point at the directory containing the project.
9. Tell Eclipse that the project uses git.
   • Select all the projects, and then right click. Select “Team” and then “Share Project...” The default opens are correct.
   • Do not use “Share Projects” (plural). This is for adding a new form of sharing.
10. Handle the issue described in the ticket...
11. Add your changes to the staging area of your local repository.
    • for an interactive add

    git add -i

    • to add specific files

    git add <filename>

12. Commit your changes to your local repository

    git commit -m "<ticket id>: <commit message>"

13. Push the changes in your branch back to the origin on github.

    git push origin <branch id>

14. Change to the branch on github, and make a pull request
    • Include the URL of the ticket.
    • Be sure to check the “Commits” and “Files Changed” tabs to be sure you are sending the correct changes.
15. Request a code review on the ticket page
    • Include the URL of the pull request in the comment for the code review.
16. Wait. Someone from OpenMRS will respond to the pull request.