-
**Developer TODO (don't remove)**
- [ ] create new branch. put issue number at start of name if not a very quick fix.
- [ ] write tests. put issue number in comment
- [ ] update documentation
- [ …
-
### Description and goal
we have a hundred TODO comments in front/src
half are tagged `TS2` or `DROP V1` and will be managed during the PI11
half are sometimes 15 months old
we have to managed t…
-
### Overview
We need to manage all our marketing issues in one place, so that we can better manage the marketing issues and keep the org rep and marketing CoP involved.
### Action Items
- [x] Go …
-
## Goal
| User story |
|:---------------------------------------------------------------------------|
| As an security engineer using [Fleet's best practice GitOps](https://github.com/fleetdm/fl…
-
I'm looking for an alternative Reddit client coming from [Flow for Reddit](https://play.google.com/store/apps/details?id=com.deeptrouble.yaarreddit) that seems to have been abandoned. So far I like Re…
-
## Goal
| User story |
|:---------------------------------------------------------------------------|
| As a new Fleet user writing a query,
| I want to see copy that explains that log destinations …
-
- [x] I have looked for existing issues (including closed) about this
## Feature Request
Update example `rest-grpc-multiplex`
### Motivation
Currently, the example code in https://github.com…
-
## User Story - Business Goal
The code is littered with TODO comments that are not linked to tickets and not well understood. This TODO concerns using the `/v2/templates` route in the Template class…
-
## Goals
- [ ] The ruff pathlib checks are enabled. :information_source: In order to do that, edit the part of `pyproject.toml` marked as `TODO#89`.
- [ ] Calls to `os.path` are replace with `path…
-
We should have a linter that looks for TODO comments and ensures they have a valid GitHub issue, e.g.
```
// TODO(https://github.com/material-motion/project-name/issues/18):
// Describe TODO here
``…