Skip to content

Consider having a separate repo per explainer聽#49

Description

@tomayac

The current "mono repo" approach makes following explainers extremely tedious. Random email subject example from my Inbox:

[WebKit/explainers] Feedback (#32) 馃

I know each Issue has a label, but they don't get carried over to email notifications. My flow is to mute email notification threads I am not interested in in Gmail, sometimes on GitHub. The current way WebKit Explainers works forces me to click through to each thread to figure out what explainer it is for, and if I want to follow it or not. I'm short before declaring email bankruptcy.

Thanks for your consideration! If it's just me, happy for others to share their (email-notification-based!) workflow. Maybe I just don't know the trick everyone else knows.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

metaissues about this repository itself

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions