Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

PRs should be opened in order #43

Open
taneliang opened this issue Aug 15, 2020 · 0 comments
Open

PRs should be opened in order #43

taneliang opened this issue Aug 15, 2020 · 0 comments
Labels
domain: CollaborationPlatform importance: 1 - must have Must be implemented for the product to be complete urgency: 3 - no urgency We have an indefinite amount of time to complete this work type: implementation A task that primarily involves bashing code
Milestone
Launch

Comments

@taneliang
Copy link
Owner

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

image
@taneliang taneliang added this to the Launch milestone Aug 15, 2020
@taneliang taneliang added importance: 1 - must have Must be implemented for the product to be complete work type: implementation A task that primarily involves bashing code urgency: 3 - within 2 weeks domain: CollaborationPlatform urgency: 2 - we can wait urgency: 3 - no urgency We have an indefinite amount of time to complete this and removed urgency: 3 - within 2 weeks urgency: 2 - we can wait labels Aug 15, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
domain: CollaborationPlatform importance: 1 - must have Must be implemented for the product to be complete urgency: 3 - no urgency We have an indefinite amount of time to complete this work type: implementation A task that primarily involves bashing code
Projects
None yet
Milestone
Launch
Development

No branches or pull requests
1 participant
@taneliang