Closed iamunknown2 closed 7 years ago
oh god this PR is dependent on #249 why is everything so complicated
oh god this PR is dependent on #249 why is everything so complicated
It isn't that hard to merge - there's a merge button right on this page...
oh god this PR is dependent on #249 why is everything so complicated
It isn't that hard to merge - there's a merge button right on this page...
yeah but if we merged this before 249 then it would probably break everything
yeah but if we merged this before 249 then it would probably break everything
I've tested a merge of my branch with gh-pages locally, and there doesn't seem to any merge conflicts.
okay good, the thing that was scaring me was
it's set to merge into the branch rework-blocks... remember that the branch #249 is merging is on Airhogs777/elemental, and the rework-blocks branch on this repo is just for testing
we'll just have to make sure to manually merge it with gh-pages instead of hitting the "merge PR" button which will probably send it to rework-blocks
see this is what it actually looks like because it's based on the changes made in my PR
What's wrong with merging this into 249?
Because 249 isn't merging in ElementalCode/elemental:rework-blocks, it's merging in Airhogs777/elemental:rework-blocks
ok so this is why we should have a single repo and only branch off the main repo
true
but also merging a PR into another PR feels wrong
@Airhogs777 can you talk on discord rn
@Airhogs777 Ok, PRs fixed and stuff. I feel like merging a branch into another non-master branch is fine via PR provided it's someone who's trying to make changes to your stuff - at which point it's up to you to determine whether to merge it
Sorry I'm at work and just saw this. Thanks for fixing this
…, but helper layer in intro.js is now off for a tutorial step when the offset is activated.