Skip to content
This repository was archived by the owner on May 22, 2023. It is now read-only.
This repository was archived by the owner on May 22, 2023. It is now read-only.

Improve how dependent PRs are managed #635

@wal001

Description

@wal001

Hey there ✋
Actually this is a suggestion to improve how dependent PRs are handled in this project. Example of a PR that depends on another one: #634. And after a quick search, you can easily find several other PRs like this.

Solution I'd like to share
Introduce to this project Dpulls, a Github app that make it easier to manage dependent PRs. Basically:

  • 🌟 It prevents a PR to be merged before its dependencies.
  • 👀 It gives more visibility to the developers so they know why a PR cannot be merged.
  • ❤️ Avoid any accidental merge that can break your master branch.

In addition to that:

  • Dpulls has support for cross-referencing (dependency from another project).
  • Doesn't require any special config to add.
  • Nothing to change in your current workflow. As you usually do, just write Depends on: #pr or Depends on: owner/repo#pr if from another project, and Dpulls will do the job 💪.

Dpulls in action 🚀 :

dependency (1)

I hope that you will like this suggestion ☺️

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions