-
Notifications
You must be signed in to change notification settings - Fork 3
PRs should be opened in order #43
Copy link
Copy link
Open
Labels
domain: CollaborationPlatformimportance: 1 - must haveMust be implemented for the product to be completeMust be implemented for the product to be completeurgency: 3 - no urgencyWe have an indefinite amount of time to complete thisWe have an indefinite amount of time to complete thiswork type: implementationA task that primarily involves bashing codeA task that primarily involves bashing code
Milestone
Description
Activity
Metadata
Metadata
Assignees
Labels
domain: CollaborationPlatformimportance: 1 - must haveMust be implemented for the product to be completeMust be implemented for the product to be completeurgency: 3 - no urgencyWe have an indefinite amount of time to complete thisWe have an indefinite amount of time to complete thiswork type: implementationA task that primarily involves bashing codeA task that primarily involves bashing code
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 in order.Example of a PR stack created in a random order: MLH-Fellowship/scheduling-profiler-prototype#110