modular / modular/stack-pr

Save links to the first PR comment instead of PR description

Open
#92 0 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
569
Forks
43
PR merge metrics
No merged PRs in 30d

Description

Github supports automerging of PRs when CI checks and other requirements are met. Using stack-pr with automerging means the full PR description, including the links to the other PRs in the stack will get merged in the main branch. The alternative I am requesting is to save the PR links to a comment in the just opened PR. This will be the first comment given the PR was just opened, so no risk there. This will keep the commit messages clean.

This depends on the following setting being enabled:

Image

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating the code path that creates a new GitHub PR and assembles its description, then trace how the stack links are generated. Done means the links are written to the first PR comment instead of the description while the stated setting is enabled; check the repository's existing tests for the relevant behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
github, python
Domain
devtools
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.