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.

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

Merged
merged 5 commits into from
Jun 22, 2020
Merged

Conversation

LukasWikander
Copy link
Collaborator

I also cleaned up the section above.

@LukasWikander LukasWikander requested a review from viktorjo June 18, 2020 12:23

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?
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

itsbigbraintime.jpg

Copy link
Member

@konglobemeralt konglobemeralt left a 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.

@LukasWikander LukasWikander merged commit 6d54176 into dev Jun 22, 2020
@LukasWikander LukasWikander deleted the bugfix_clarifyPullRequestWorkflow branch June 22, 2020 08:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants