Skip to content

[Fixes #69] Nav Toolbar Issue#14

Open
abulojoshua1 wants to merge 1 commit into
masterfrom
issue_69_nav_toolbar_issues
Open

[Fixes #69] Nav Toolbar Issue#14
abulojoshua1 wants to merge 1 commit into
masterfrom
issue_69_nav_toolbar_issues

Conversation

@abulojoshua1
Copy link
Copy Markdown
Owner

@abulojoshua1 abulojoshua1 commented Sep 2, 2020

Nav Toolbar Issue

Checklist

Reviewing is a process done by project maintainers, mostly on a volunteer basis. We try to keep the overhead as small as possible and appreciate if you help us to do so by completing the following items. Feel free to ask in a comment if you have troubles with any of them.

For all pull requests:

  • Confirm you have read the contribution guidelines
  • You have sent a Contribution Licence Agreement (CLA) as necessary (not required for small changes, e.g., fixing typos in the documentation)
  • Make sure the first PR targets the master branch, eventual backports will be managed later. This can be ignored if the PR is fixing an issue that only happens in a specific branch, but not in newer ones.

The following are required only for core and extension modules (they are welcomed, but not required, for contrib modules):

  • There is a ticket in https://github.com/GeoNode/geonode/issues describing the issue/improvement/feature (a notable exemption is, changes not visible to end-users)
  • The issue connected to the PR must have Labels and Milestone assigned
  • PR for bug fixes and small new features are presented as a single commit
  • Commit message must be in the form "[Fixes #<issue_number>] Title of the Issue"
  • New unit tests have been added covering the changes, unless there is an explanation on why the tests are not necessary/implemented
  • This PR passes all existing unit tests (test results will be reported by travis-ci after opening this PR)
  • This PR passes the QA checks: flake8 geonode
  • Commits changing the settings, UI, existing user workflows, or adding new functionality, need to include documentation updates

Submitting the PR does not require you to check all items, but by the time it gets merged, they should be either satisfied or inapplicable.

@codecov-commenter
Copy link
Copy Markdown

Codecov Report

Merging #14 into master will increase coverage by 1.65%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master      #14      +/-   ##
==========================================
+ Coverage   57.34%   59.00%   +1.65%     
==========================================
  Files         184      184              
  Lines       20567    20567              
  Branches     3415     3415              
==========================================
+ Hits        11794    12135     +341     
+ Misses       7730     7359     -371     
- Partials     1043     1073      +30     

@abulojoshua1 abulojoshua1 force-pushed the issue_69_nav_toolbar_issues branch from 928a544 to f3a4e85 Compare September 7, 2020 08:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants