Skip to content

Fixes https://github.com/GeoNode/geonode-project/issues/562 Backup.sh procedure is just able to run once#13215

Open
kikislater wants to merge 1 commit into
GeoNode:masterfrom
kikislater:patch-8
Open

Fixes https://github.com/GeoNode/geonode-project/issues/562 Backup.sh procedure is just able to run once#13215
kikislater wants to merge 1 commit into
GeoNode:masterfrom
kikislater:patch-8

Conversation

@kikislater

Copy link
Copy Markdown
Contributor

Fixes GeoNode/geonode-project#562 @caocuongngo

For all pull requests:

  • [x ] 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"
  • PR title must be in the form "[Fixes #<issue_number>] Title of the PR"
  • 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: black geonode && flake8 geonode
  • Commits changing the settings, UI, existing user workflows, or adding new functionality, need to include documentation updates
  • Commits adding new texts do use gettext and have updated .po / .mo files (without location infos)

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.

@cla-bot cla-bot Bot added the cla-signed CLA Bot: community license agreement signed label May 28, 2025
@codecov

codecov Bot commented May 28, 2025

Copy link
Copy Markdown

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 72.59%. Comparing base (03a6578) to head (61a5e67).

Additional details and impacted files
@@            Coverage Diff             @@
##           master   #13215      +/-   ##
==========================================
- Coverage   72.59%   72.59%   -0.01%     
==========================================
  Files         916      916              
  Lines       52636    52636              
  Branches     6058     6058              
==========================================
- Hits        38212    38210       -2     
- Misses      12857    12860       +3     
+ Partials     1567     1566       -1     
🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@giohappy

Copy link
Copy Markdown
Contributor

@etj you put a comment in GeoNode/geonode-project#562 (comment).
Is this PR aligned with it?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

cla-signed CLA Bot: community license agreement signed

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Backup.sh procedure is just able to run once

4 participants