[~aloraine]
I have accidentally added the commit to the master branch and was unable to revert the change. Please tell me if I need to do anything to fix it.
Because of earlier mistakes regarding the commit message, I have two commits which are doing the same thing.
I apologize for any inconvenience
https://bitbucket.org/Gchamma/integrated-genome-browser/commits/

I would do some research into how to undo a commit after it's been pushed to "origin" or another remote repository.

I think you can undo it maybe using git reset.

Enroll the Canvas class and do the "git" module. I'm pretty sure it covers git reset. Do the learn git branching tutorial a couple times until it sinks in. It is the best thing there is for learning git. Git is brilliant and powerful, but it takes time to understand it in a deep way.

Also: Google "how to undo a commit to master branch after I pushed to my fork"

Commit and branch created, and the installer was downloaded and tested.
Ready for 1st-level review.
https://bitbucket.org/Gchamma/integrated-genome-browser/commits/edfe0dfcba3d72499b80db8686d97b4c087aac9e

Jay Chamma please note:

Ticket is in "Ready for Pull Request" column. No notes have been added explaining what testing was done by the reviewer (Nowlan Freese) which is not ideal, but for very lightweight changes such as this, it's OK.

I have merged PR submitted by Logan Weidenhammer which touches the same line of code.

Jay Chamma: Please rebase your branch onto master. Note there will be a conflict during the rebase, which is fine – you'll just need to manually edit the line to ensure your change and Rachel's change are both present.

[~aloraine]
Rebased and resolved the conflict successfully, please review the following commit:
https://bitbucket.org/Gchamma/integrated-genome-browser/commits/0cce23ae0983f44d49d983aafa4a782da07ce309

Please re-read https://canvas.instructure.com/courses/1164217/pages/understand-igb-development-workflow?module_item_id=12709540.

When done, the developer pushes their commits changes to the topic branch to their fork, which should be configured to automatically build a branch-specific installers. (Instructions on for configuration are covered elsewhere.)

Once the installer is built, developer adds a link to their topic branch to the Jira issue as a Comment. They then move the issue into the next column - "Needs 1st Level Review" - and un-assigns the issue. This signals to everyone else that the issue is now ready for review, and anyone with time and expertise can pick it up.

You need to include a link to your branch and also you need to un-assign the ticket when you move it to "Needs 1st Level Review"

[~aloraine]
Moved to need first level review column, unassigned the ticket, and the Installer is working successfully.
Branch link: https://bitbucket.org/Gchamma/integrated-genome-browser/branch/IGBF-2412

I looked at the commit and the branch. It includes the latest code (from Rachel) and adheres to coding standards. I did not download or run the code, but I am confident it works. Recommending pull request.
cc: Jay Chamma

[~aloraine]
Pull request submitted
Link: https://bitbucket.org/lorainelab/integrated-genome-browser/pull-requests/800/igbf-2412-add-name-to-credits/diff

Merged.

Tested on master branch.

Galal Chamma shows up in credits.