Skip to content

Add script to generate knowledge card content

Edouard Legoupil requested to merge feature-many-to-many-knowledge-references into main_dev

Created by: Edouard-Legoupil

This commit introduces a new command-line script to automatically generate content for knowledge cards that are missing it or have outdated information based on their references.

Key changes include:

  • A new script backend/scripts/generate_card_content.py has been added. This script iterates through all knowledge cards and, for each card, determines if a content update is needed based on whether the generated_sections field is empty or if any of its associated references have been updated more recently than the card itself.

  • The script uses the ContentGenerationCrew to generate new content for the sections.

  • The script accepts a --force argument to force the regeneration of content for all knowledge cards.

  • The populate_knowledge_cards.py script has been updated to set a default template_name for the knowledge cards.

  • Does my code meet the quality standards for releasing packages?

  • Does the reviewer have all the information to validate the features/issues without too much research?

  • Does the customer who will validate the associated tickets have the information to do so without wasting time?

Issues to validate to close :

  • issue #

Processed issues to keep open or in progress:

  • issue #

Checklist:

  • Does the package check go local?
  • Does the CI pass?
  • Are the added / fixed features documented, tested?
  • Are the added features / solved problems briefly presented in the PR message?
  • Are the changes related to tickets / issues that I have listed in the commits and in the PR itself?
  • Are the tickets in "review" mode in the Project Tracking Board?
  • Does each ticket, if it is to be closed after acceptance of the PR, contain a comment that tells how to validate it?

Merge request reports