-
Notifications
You must be signed in to change notification settings - Fork 38
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
Update from master #854
Update from master #854
Conversation
v1.11.0 Release
Add Github issue templates
Add initial pull request template
Create initial contributing guidelines
@danieliser Normally, I would have gone from the tag of the version created but I also wanted to merge the new issue and pull request templates as I wanted to add to them as I completed other tasks during the 1.12 release which is why I merged from Was there a better way to achieve that? |
@fpcorso Ahh, probably the "right" way would have been to make them features off of develop and merge them when we did a normal release, but this may be an exception to the rule as that doesn't fit the normal flows. |
Next time maybe just merge the tag like normal, then merge your side branches and then back merge master again into develop. This way the normal release flow stays in tact and you can push changes directly to master and back to develop without worry. |
Update develop with changes from master