Elgato_dark/fleet
1
0
Fork 0
mirror of https://github.com/fleetdm/fleet synced 2026-05-24 09:28:54 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 32

Handbook: Update drafting steps (#22286)

Browse source 
- Update where to make reference doc PRs (use reference doc release
branch)
- Point toward story issue template re: what to link to in issues (since
it's always evolving)
This commit is contained in:
Rachael Shaw 2024-09-22 15:18:01 -05:00 committed by GitHub
parent d7594d1f1d
commit b26c592143
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
1 changed files with 2 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
handbook/product-design/README.md
View file

@ -36,9 +36,9 @@ At Fleet, like [GitLab](https://about.gitlab.com/handbook/product-development-fl
- **Ready.** Use this page to communicate designs reviews and development.
- **Scratchpad.** Use this page for work in progress and design that might be useful in the future.
- If the story requires API or YAML file changes, open a draft PR with the proposed design.
- If the story requires API or YAML file changes, open a pull request to the reference docs release branch (e.g. `docs-v4.58.0`) with the proposed design. Mark the PR ready for review as soon as it's ready for feedback from the [API design DRI](https://fleetdm.com/handbook/company/communications#directly-responsible-individuals-dris).
- Add links to the Figma file's cover page and draft PRs in the user story.
- Add links to the user story as specified in the [issue template](https://github.com/fleetdm/fleet/issues/new?template=story.md).
- Draft changes to the Fleet product that solve the problem specified in the story. Constantly place yourself in the shoes of a user while drafting changes. Place these drafts in the appropriate Figma file in Fleet product project.