GitHub Workflow

GitHub Issues & Pull Requests

Repo: https://github.com/oyuh/fivelaunch

This repo uses GitHub Issues for bug reports / feature requests and Pull Requests for code changes.

Issues: https://github.com/oyuh/fivelaunch/issues
New issue: https://github.com/oyuh/fivelaunch/issues/new/choose
Pull requests: https://github.com/oyuh/fivelaunch/pulls

Before you open anything

Search existing issues first.
If it’s a crash/bug, try to reproduce it with:
- FiveM and GTA fully closed before launch
- a fresh client profile
- pluginsMode: sync if it involves ReShade

How to create a good Issue

Issue title

Keep it short and specific:

✅ ReShade preset path breaks in junction mode
✅ GTA settings reset after launch on OneDrive Documents
❌ Doesn't work

Issue body format (copy/paste)

## Summary
(1-2 sentences describing the problem)

## What I expected

## What happened

## Steps to reproduce
1.
2.
3.

## Environment
- OS: Windows 10/11
- FiveLaunch version: (from Releases)
- FiveM install path: (the folder containing FiveM.app)
- FiveLaunch gamePath override set?: yes/no
- Client link options:
  - mods: true/false
  - plugins: true/false
  - pluginsMode: junction/sync
  - citizen: true/false
  - gtaSettings: true/false
  - citizenFxIni: true/false

## Logs
Attach:
- App logs (from the Logs panel, if available)
- ReShade diagnostics (if relevant):
  `%APPDATA%\FiveLaunch\clients\<clientId>\settings\reshade\diagnostics.log`

## Screenshots / Video (optional)

What NOT to include

Personal info, tokens, passwords, or any private server access details.

How to create a Pull Request (PR)

PR title

Follow the same rule as issues: short + specific.

Examples:

Fix plugins sync cache not saving
Docs: add backup guide

PR description format (copy/paste)

## What changed

## Why

## How to test
1.
2.

## Screenshots (optional)

## Notes / follow-ups

PR checklist

Build still works (pnpm build:win if you can)
No unrelated formatting-only changes
If user-facing behavior changed, update docs under docs/