-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Undid the ReactiveRefactor listener-queue
- Loading branch information
1 parent
e4f7c80
commit b6000d2
Showing
3 changed files
with
1 addition
and
18 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
b6000d2
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please use branches for development. I also recommend pull requests and issues.
b6000d2
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi Phil,
Thanks for the reminder. I had originally made these changes in the Reactive Refactor branch, and then merged them into master (since they worked properly), but later on, I found out that they were damaging to other parts of the code, so I then removed them from master. Henceforth, we will use pull requests when we merge branches into master.
b6000d2
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
First, everyone has to roll back commits at one time or another. In your case, it sounds like you don't have enough tests running before you merge.
Second, rolling back changes is one way to solve the problem, but if you added a useful feature, you should try to find the bugs in the system instead of simply reverting. I know that at this time it may be necessary to roll back so that the rest of the team can continue to work.