Skip to content

Fix frontend update process. Closes #795#799

Merged
regulartim merged 2 commits intodevelopfrom
fix_frontend_update
Feb 12, 2026
Merged

Fix frontend update process. Closes #795#799
regulartim merged 2 commits intodevelopfrom
fix_frontend_update

Conversation

@regulartim
Copy link
Copy Markdown
Collaborator

Description

This changes the flags of collectstatic:

  • add --clear to fix the actual problem; the frontend files are now refreshed on every start of GreedyBear
  • add --verbosity 0, otherwise every updated file is getting logged

I also added an echo of the GreedyBear version number, this might make debugging easier in the future.

Related issues

Type of change

Please delete options that are not relevant.

  • Bug fix (non-breaking change which fixes an issue).
  • New feature (non-breaking change which adds functionality).
  • Breaking change (fix or feature that would cause existing functionality to not work as expected).

Checklist

  • I have read and understood the rules about how to Contribute to this project.
  • The pull request is for the branch develop.
  • I have added documentation of the new features.
  • Linter (Ruff) gave 0 errors. If you have correctly installed pre-commit, it does these checks and adjustments on your behalf.
  • I have added tests for the feature/bug I solved. All the tests (new and old ones) gave 0 errors.
  • If changes were made to an existing model/serializer/view, the docs were updated and regenerated (check CONTRIBUTE.md).
  • If the GUI has been modified:
    • I have a provided a screenshot of the result in the PR.
    • I have created new frontend tests for the new component or updated existing ones.

Important Rules

  • If you miss to compile the Checklist properly, your PR won't be reviewed by the maintainers.
  • If your changes decrease the overall tests coverage (you will know after the Codecov CI job is done), you should add the required tests to fix the problem
  • Everytime you make changes to the PR and you think the work is done, you should explicitly ask for a review. After being reviewed and received a "change request", you should explicitly ask for a review again once you have made the requested changes.

@regulartim regulartim requested a review from mlodic February 12, 2026 06:58
@regulartim regulartim marked this pull request as ready for review February 12, 2026 06:58
@regulartim regulartim merged commit 7917a1e into develop Feb 12, 2026
4 checks passed
@regulartim regulartim deleted the fix_frontend_update branch February 12, 2026 17:07
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.

2 participants