Skip to content

[fork-setup] Prepare how we'll merge PRs / how to communicate with PR authors #9

@bew

Description

@bew

Prepare how we'll merge PRs

I think I'd like to avoid duplicating PRs that are being worked on Wezterm (by default), so they can continue working there.

👉 FIXME: is this a bad idea?

When a PR is ready (is marked Approved in our PR triage project), we could copy the PR to RezTerm, run our CI and merge.
👉 Need a script to help with that 🤔 (in https://github.com/rezterm-org/z-project-helpers)

Prepare how to communicate with PR authors

For PRs we're evaluating to include in the fork but that are not ready yet, we should have a prepared message to post on original PR to link to the announcement, the fork, and what they can do (re-open the PR on RezTerm and work there, or continue working on Wezterm and we'll import the PR later on 🤔).

Need message templates for these use-cases:

hello $author, we're interested to get your unfinished PR into rezterm fork (link to announcement), willing to continue working on it? (if yes.. if not..)

hello $author, we're preparing to merge your PR in rezterm fork (link to announcement), here is how to follow progress

hello $author, FYI we've merged your PR in rezterm fork (link to announcement)


WDYT?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions