Good first issues and where to start

Aperta
#192 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
1/5
Tempo stimato
Meno di un'ora
Idoneità per principianti
1/100
Tipo di issue
Documentazione
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
markdown
Ambito
documentation

Direzione di ricerca

Read CONTRIBUTING.md and docs/contributing/starter-issues.md to understand how contributions are made and where starter issues are documented. This issue is an index for other work; choose one of its linked issues and follow that issue's criteria to determine when the contribution is done.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

documentation good first issue

New to the project? This is where to start.

  1. Read CONTRIBUTING.md: how to build, test and open a pull request.
  2. Pick an issue below (the ones labelled good first issue are safe for a first contribution), and comment on it to claim it before you start.
  3. Not sure what fits you? Ask in a comment on this issue. The roadmap shows where the project is heading.

Want something bigger? Medium and large pieces of work (a few days to a week or more) are listed in #215 ("Roadmap: medium and large contributions"). Pull requests do not have to be small.

Each issue has context, "done when" criteria and pointers into the code. The full text of every starter issue is also kept in docs/contributing/starter-issues.md.

Documentation and translations
  • #163 Add a third UI language
  • #164 Make check:i18n compare every locale file
  • #165 Complete the keyboard shortcuts help
  • #166 Refresh statements in the user guide that no longer match the app
  • #167 Document connecting apps (the Apps dialog) in the user guide
  • #168 Add a README to each core crate
  • #169 Contribute example skills
  • #191 Improve error messages for the first-run provider test
Desktop UI quality and accessibility
  • #170 Add unit tests for the UI helper modules that have none
  • #171 Keyboard-only and screen-reader pass over the first-run wizard, chat and settings
  • #190 Stylelint/UI polish: audit components for raw values and missing tokens
  • #182 Run the real-app smoke harness in CI
Platforms and packaging
  • #172 macOS desktop backend: screenshots
  • #173 macOS desktop backend: accessibility tree
  • #174 macOS desktop backend: keyboard and mouse input
  • #175 Build and publish Linux and macOS desktop bundles
  • #176 Wayland support for the Linux desktop backend
  • #177 Windows on ARM64: build and installer in CI
  • #178 Winget manifest for the Windows installer
  • #179 Homebrew cask or formula
  • #180 AUR package for the Linux daemon
  • #181 Docker image for the always-on host
Apps, providers and engines
  • #183 Add more direct app connectors to the MCP catalog
  • #184 Add an LLM provider preset
  • #185 Sign in to Antigravity (agy) on a server from the desktop
  • #186 Sign in to Cursor's CLI on a server from the desktop
  • #187 Sign in to OpenCode on a server from the desktop
Core logic and tests
  • #188 Natural-language schedule parser: more phrases and a third language
  • #189 Add hermetic evaluation scenarios

Found a vulnerability? Do not file it here: see SECURITY.md.

Lingua principale
Rust
Stelle
0
Fork
1
Merge medio
6h 54m
PR unite (30g)
152

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di emreocell/Praxi-Bot

Tutte le issue di emreocell/Praxi-Bot

Issue simili

Altre issue su Rust

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.