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

Make e2e tests mandatory for PR merging

Aperta
  • Qualcosa non va?
#4,284 0 commenti 0 reazioni 1 assegnatario Vedi su GitHub

I maintainer di solito rispondono entro 3 giorni

@clairep94 ci sta già lavorando.

Dal 1/9/2026.

Valutazione

Questa issue non è ancora stata valutata.

Descrizione

Enhancement On Hold
Increasing Access

Unsure

Feature enhancement details

Context:

This issue is a followup from GSOC:

  • @Geethegreat has create an e2e test suite for his GSOC 2026 project
  • We purposely made it so that e2e tests were not required for merging PR's so that the GSOC project did not unnecessarily block other work on the repo
  • We also purposely made it so that e2e tests were gated by approval from @Geethegreat, @clairep94, @khanniie, or @raclim during the GSOC period, so that we did not accidentally overspend on GHA hours
  • Now that GSOC is complete, we should update so that the e2e test suite is mandatory for merging into develop
  • Ideally we should update to:
    • Remove the approval gating
    • Have e2e tests trigger automatically after successful unit tests
    • Add some concurrency rules to ensure this doesn't result in a lot of GHA hours useage
      • Cancel any in-progress runs if a later run is triggered
      • Maybe debounce triggers if this is possible
    • Ideally update to minimize the required amount of time for e2e tests to run:
      • Make app startup in CI faster if possible
      • Caching any installations (some work previously done here already)

--> Will self-assign this issue

Requirements:

  • Access to repo settings > environments & branch protection
Lingua principale
JavaScript
Stelle
1.7k
Fork
1.7k
Merge medio
2g 7h
PR unite (30g)
8

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 processing/p5.js-web-editor

Tutte le issue di processing/p5.js-web-editor

Issue simili

Altre issue su JavaScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.