-
Notifications
You must be signed in to change notification settings - Fork 102
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 next
branch
#271
Update next
branch
#271
Conversation
* Add WASM section to README * Use wasm feature * Fix * [no ci] Changelog update * Revert test changes
* Update version * Add load_tmx_map_from note * Fix copypasta * Fix indentation * Change version in README
* Remove outdated doc * Update changelog
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.
Approved, but please don't use GitHub to merge current
into next
, since it should be possible to simply fast-forward next
to current
given that there is no new work submitted to next
yet.
How can I do that if the base branch is protected? |
I wasn't sure so I just tried it. This seems to have worked, and automatically closed this PR as merged:
I'm not sure exactly why this works. Maybe it is because an approved PR was open, or maybe it is because I'm admin. To be sure we could try it without PR next time the branch can just be fast-forwarded, and next time you try this. :-) |
I tried exactly that yet Github denied my push. Pretty sure it's because you're an admin. |
No description provided.