Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

🙏 State stuff

Aperta
  • Qualcosa non va?
#1,908 5 commenti 1 reazione 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
25/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Tranquilla
Stack tecnologico
github, powershell
Ambito
devops, testing

Direzione di ricerca

Start by reading the Maester test reporting and JSON result handling entry points, then trace how tests and their output are represented. The issue proposes comparing a previous JSON result and optionally using GitHub Issues as a state store, but does not name specific files or tests. Done would include reporting new failures and fixed tests, with the GitHub issue behavior and ignored tests clarified.

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

Descrizione

enhancement report
Describe the feature

Have some sort of understanding of state in Maester would be great, a lot of people are asking about: "what has changed"? and "Can I see new failing tests?" and "Can I ignore tests"?

I want maester to have understanding of state, and introduce new states fixed, failing, new-failing

For the first version I propose to accept the previous json result as "previous state", and I also want to make a second state store using GitHub Issues. Also this should guide others in setting up their own state stuff, like having an interface.

Impact and importance

Having state is a very big ask, so I guess it is important for a lot of people. Having the report tell you which issues have been fixed should give a great feeling.

Alternatives you've considered

No response

Additional context

I'll be building this with the help of AI, and validating whats built myself

I want Maester to have a state component with the following requirements:

Save current state Compare to previous state The reports should be expended with test that suddenly fail, test that stopped failing (are fixed) and new tests specify the previous json as one way to compute the state Using github issues in a secific repository as a second way to compute state, one issue per failing test, not sure if I want issues for test that pass, maybe that should be an option Plan first and ask questions/confirmation before coding

When using github issues, set the title to the name of the test, tag the issue with the tags from that test (orca, cis, ....). With github issues set the description to the test output, and if the issue is closed by the user. You can mark this test as ignored.
Lingua principale
PowerShell
Stelle
1.1k
Fork
288
Merge medio
20h 23m
PR unite (30g)
166

Preparare l'ambiente

Apri in Codespaces

Avvia il container di sviluppo del progetto nel browser, con il tuo account GitHub.

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 maester365/maester

Tutte le issue di maester365/maester

Issue simili

Altre issue su DevOps

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.