Nico
c0d39f7690
<!-- Add the related story/sub-task/bug number, like Resolves #123, or remove if NA --> **Related issue:** Resolves #42651 # Checklist for submitter - [x] Changes file added for user-visible changes in `changes/`, `orbit/changes/` or `ee/fleetd-chrome/changes`. See [Changes files](https://github.com/fleetdm/fleet/blob/main/docs/Contributing/guides/committing-changes.md#changes-files) for more information. ## Testing - [x] Added/updated automated tests - [x] QA'd all new/changed functionality manually ## New Fleet configuration settings - [x] Verified that any relevant UI is disabled when GitOps mode is enabled <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **New Features** * Added "Continuous" option for policy automations to re-run script/software automations on every subsequent failure. * Editable automations available directly from policy create, edit, and details pages. * New modal and field flows for managing automations (webhook/ticket, calendar, conditional access) and a Patch automation CTA for patch policies. * **Improvements** * Redesigned automations UI, table cell rendering, and list/footer messaging for clarity. * Various styling and layout refinements for consistent behavior and overflow prevention. <!-- end of auto-generated comment: release notes by coderabbit.ai -->
assets Directory
This directory is used by the frontend build tool to store generated frontend build assets, such as JavaScript bundles, CSS files, and other static resources (images, fonts, etc.) that are produced during the build process.
Key Points
- Do not commit generated files: All files in this directory are generated automatically and are git-ignored. They should not be committed to version control.
- Not for static files: Do not place unrelated static files (like PDFs, config profiles, or documentation) here. Use a separate directory for non-UI assets.
- Regenerated on build: These files are recreated every time you run the frontend build process.