Conversation
- Updated permissions to allow program managers to log sessions when direct-service staff are unavailable. - Added tests to verify that program managers can access and submit group session logs.
…rt command The Info/Profile tab gated the custom fields section on `custom_data` being non-empty, but `hide_empty=True` filtered out all valueless fields — so the entire section (including the Edit button) never rendered for new participants. Now the section renders whenever editable custom field groups exist, showing the existing "Click Edit to add information" prompt. Also adds `import_custom_fields` management command for importing custom field groups and definitions from a JSON file. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Public repos inherit the repository-level default GITHUB_TOKEN permissions. Explicitly set contents: read so fork PRs can never escalate privileges if repo defaults change. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Restrict CI workflow to read-only permissions
Public repo action logs were exposing infrastructure details (resource group, scaling config, probe settings, creator email) from the full JSON response. Add --output none to silence it. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
All four workflows now explicitly set permissions: contents: read, matching the hardening already applied to ci.yml and qa-scenarios.yml. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Enhance session logging for program managers and CI permissions
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This pull request introduces significant performance and maintainability improvements to the
apps/admin_settings/demo_engine.pydemo data seeding engine, as well as minor updates to GitHub workflow files for improved permissions and output handling. The main changes focus on optimizing plan and note generation, adding detailed stage timing logs, and enabling efficient bulk database operations. These updates should make demo data generation faster, more transparent, and easier to debug.Demo Engine Improvements:
Performance and Caching:
ProgressNoteTargetandMetricValueobjects in the note generation process, significantly reducing the number of database writes and improving performance for large demo datasets.Maintainability and Extensibility:
author_roleandepisode), supporting more flexible and accurate demo data creation. [1] [2]Instrumentation and Logging:
timed_stagecontext manager and integrated it throughout the mainrunorchestration method. This provides precise start/end timing logs for each major data seeding stage, aiding in performance monitoring and troubleshooting. [1] [2] [3]GitHub Workflow Updates:
Security and Output Handling:
permissions: contents: readto all workflow YAML files to explicitly declare required GitHub token permissions, improving security posture. [1] [2] [3]build-push-acr.ymlto suppress output (--output none), reducing log noise during deployments.