Files

T

Victor Lyuboslavsky fe24ff1d67 Fixed a bug where certain macOS app names could be ingested as empty strings due to incorrect ".app" suffix removal. (#39563 )

<!-- Add the related story/sub-task/bug number, like Resolves #123, or
remove if NA -->
**Related issue:** Resolves #34620

# Checklist for submitter

- [x] Changes file added for user-visible changes in `changes/`,
`orbit/changes/` or `ee/fleetd-chrome/changes`.

## Testing

- [x] QA'd all new/changed functionality manually


<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->

## Summary by CodeRabbit

## Bug Fixes
* Fixed an issue where macOS app names could become empty after removing
the ".app" extension. The app name extraction logic now correctly
handles edge cases, ensuring app names are properly ingested without
empty values.

<!-- end of auto-generated comment: release notes by coderabbit.ai -->

2026-02-10 13:03:23 -06:00

adr

ADR-0008: Migrate from go-kit/log to slog (#38751 )

2026-01-26 15:50:31 -06:00

architecture

oncall doc updates (#39517 )

2026-02-09 10:43:27 -05:00

assets

Document research for Android agent app (#35094 )

2025-11-24 12:10:40 +01:00

getting-started

Add Testing NATS logging local development docs (#37759 )

2026-01-06 09:11:58 -03:00

guides

Update MDM instructions in design QA considerations (#38371 )

2026-01-15 09:54:02 -06:00

product-groups

Fixed a bug where certain macOS app names could be ingested as empty strings due to incorrect ".app" suffix removal. (#39563 )

2026-02-10 13:03:23 -06:00

reference

Added contributor docs for SigNoz. (#39402 )

2026-02-09 15:28:28 -06:00

research

Document research for Android agent app (#35094 )

2025-11-24 12:10:40 +01:00

responsibilities

…

rituals

Add PR review to daily standup, remove incoming bug triage (#37090 )

2025-12-11 15:31:51 -06:00

workflows

Releasing Fleet steps: Wrong Helm chart (#37051 )

2025-12-10 14:53:10 -06:00

README.md

Update contrib docs headers to sentence case (#29276 )

2025-05-20 11:26:35 -05:00

README.md

Fleet Contributor Documentation

Welcome to the Fleet contributor documentation! This documentation is designed to help you contribute to the Fleet project.

Documentation structure

The documentation is organized into the following sections:

Getting Started - Setup, building, and testing Fleet
Guides - How-to guides for common tasks
Architecture - High-level architecture documentation
Product Groups - Documentation for specific product groups
Workflows - Development workflows
Reference - API reference, configuration, etc.
ADRs - Architectural Decision Records
Research - Research documents for product groups
Responsibilities - Responsibility documents for product groups

Product groups

Fleet is organized into three main product groups:

MDM - Mobile Device Management
Orchestration - Device orchestration using osquery
Software - Software inventory, vulnerability management, and software installation

Contributing

If you're new to Fleet, we recommend starting with the Getting Started section to set up your development environment.

Once you're set up, you can explore the Guides section to learn how to contribute to specific areas of the project.

Architectural Decision Records (ADRs)

We use Architectural Decision Records to document significant architectural decisions. If you're making a significant architectural change, please create an ADR to document your decision.