E-Liang Tan

If there's a merge commit above the earliest interesting commit, our frontend vomits blood. ## Steps to repro 1. Clone repro repo: https://github.com/24r/stack-attack-issue-44-repro. These are the branches: - `main`: the...

This is a big one that'll need to be broken down further. The frontend already supports showing PR info, Stacker/CollabPlatform just need to feed it data.

The config file is currently being read in multiple places. Apart from being unclean, it may also introduce bugs as we don't validate inputs, causing weird crashes in random places...

Currently, updating the PR description will replace the whole description. Users will want to add custom text to their PRs, e.g. a summary and test plan like in https://github.com/MLH-Fellowship/scheduling-profiler-prototype/pull/111. Here's...

Currently, PRs are opened in an indeterminate order, because we're creating the PRs in a `Promise.all`. We should do this sequentially instead as users will expect them to be created...

Currently, they're hardcoded to `master`. This should be set to the closest long-lived branch, or the branch of the PR above it in the stack.

As discussed in a 8:30pm SGT call with @saphal1998. In our command line UI, show these branch types: - Local long lived branches - Remote long lived branches - Local...

"origin" is currently hardcoded in some places, but we need to support other remote names so that we can support the [forking workflow](https://guides.github.com/activities/forking/) that's common on GitHub.

Stack Attack only supports pushing to SSH remotes now. HTTPS remotes should be supported as they are commonly used.