USER_STORY_Navigation_Bar_#74: Issue(please closed this one)

[kaimanasse15]

Pull requests should follow a common structure for organizational purposes and quick readability.

Naming convention for PR titles

< repo > _ < sprint > _ < issue > _ < pr or issue name >

Example:
belindas-closet-android_2_5_landing-page
This would be for the belindas-closet-android repo, sprint 2, issue 5, with the name "landing page."\

When first submitting your pull request, make sure to assign it on github to your team members who will be responsible for validating your pull request and make sure there are no merge conflicts.

After assigning to a particular member set, we can then assign it to a proper project if you are working across multiple repos. This is especially important for the above reason, and is a fantastic way to organize your pull requests without mixing up where they are intended to go.

We can also assign a label to the pull request. This lets your PM/PO/ etc know what this pull request applies to. This makes assessing what we're looking for very quick and easy as a Project Manager, or other leader within the team.

**When submitting your pull request, be descriptive in both your topic name (IntelliJ Configuration(s)) and also assign it to a numbered issue. In this case, we've assigned this #12, because at the time of creation, there were 11 issues, and this was the logical next number to assign it to.

Ensure you include details. As I did the following: <insert steps, include images if applicable>

When submitting a comment for a pull request, please label your pull request as a solution to another issue.

For example, reference the below image, and what I have put into the comment that will resolve our number 12 issue of no .idea file that's ignored in our .gitignore file.

We also want to include unit tests if and when possible to make sure we're getting full coverage of our code. This will simulate a real world environment where tests are extremely important.

Unit Test Example