-
Notifications
You must be signed in to change notification settings - Fork 4
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.
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
Clarify pull request workflow #265
Conversation
June release, version 0.5.0
|
||
11. Merge the pull request into the **staging** or **feature** branch, and then delete it on github. | ||
12. Run applicable test again on the merged code. | ||
* Is a triple nested ternary really necessary or is a two liner easier to comprehend? |
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.
itsbigbraintime.jpg
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.
A lot of good additions and improvements to the old text. Lets try to follow this as much as we can! Added some suggestions to point out that the Util repo should perhaps also be part of the last "pull sequence" to ensure everything is working with the latest iteration of util.
Co-authored-by: Jesper Blidkvist <[email protected]>
Co-authored-by: Jesper Blidkvist <[email protected]>
I also cleaned up the section above.