Skip to content

Conversation

@2m
Copy link
Contributor

@2m 2m commented Oct 1, 2016

No description provided.

Copy link
Member

@sjrd sjrd left a comment

Choose a reason for hiding this comment

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

Thanks. Could you amend your commit with the following tiny change, and force-push your branch? (don't create a second commit)


@p
then enjoy the types available in @hl.scala{org.scalajs.dom}. scalajs-dom 0.9.0 is built and published for Scala.js 0.6.6 and later, with both Scala 2.10 and 2.11.
then enjoy the types available in @hl.scala{org.scalajs.dom}. scalajs-dom 0.9.1 is built and published for Scala.js 0.6.6 and later, with both Scala 2.10 and 2.11.
Copy link
Member

Choose a reason for hiding this comment

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

You should also change Scala.js 0.6.6 -> 0.6.8 in that case.

@2m
Copy link
Contributor Author

2m commented Oct 6, 2016

Done. Amended and force pushed.

You can also squash using github UI before merging. Does that not produce wanted results?

@sjrd sjrd merged commit ccbe8c9 into scala-js:master Oct 6, 2016
@sjrd
Copy link
Member

sjrd commented Oct 6, 2016

No squashing from GitHub does not produce a merge commit. We want merge commits to identify groups of commits pertaining to a PR.

@2m 2m deleted the patch-1 branch October 6, 2016 19:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

2 participants