Address minor errors from #125 and #170

[agitter]

Did you add yourself as a contributor if this is your first contribution?

• Yes, I added myself or am already a contributor

Any more details?
(see below)

[agitter]

Previous builds had the error ERROR: No anchor #blackbox for internal URI reference (e.g. https://travis-ci.org/Benjamin-Lee/deep-rules/builds/509764376#L2191). Adding a newline after the sub-section header seemed to fix this. @dhimmel is that the expected behavior?

I also switched the CI badge, which was updated in #170 to the new rootstock CI but not the CI for this repository.

Interestingly, it looks like draft pull requests on GitHub don't trigger CI builds on travis-ci.org. It works with the new travis-ci.com GitHub app.

[agitter]

@dhimmel I'm also wondering whether we should revert the ci/deploy.sh changes from travis-ci.org to travis-ci.com.

[dhimmel]

Ah yes these two lines are wrong:

deep-rules/ci/deploy.sh

Lines 52 to 53 in 1b43084

	https://travis-ci.com/$TRAVIS_REPO_SLUG/builds/$TRAVIS_BUILD_ID
	https://travis-ci.com/$TRAVIS_REPO_SLUG/jobs/$TRAVIS_JOB_ID

They should be .org... my bad... have made this mistake in many places.

[dhimmel]

Interestingly, it looks like draft pull requests on GitHub don't trigger CI builds on travis-ci.org. It works with the new travis-ci.com GitHub app.

Drafts do trigger CI on travis-ci.com? IIRC draft PRs haven't triggered any travis builds for me. A real annoying bug. I didn't see an issue here, but we probably should open one.

[dhimmel]

Adding a newline after the sub-section header seemed to fix this. @dhimmel is that the expected behavior?

All the pandoc examples of header identifiers in the docs aren't directly followed by text. It doesn't seem to mention a newline is necessary, but perhaps this is intended. It could also be a pandoc bug.

[agitter]

They should be .org... my bad... have made this mistake in many places.

No problem, updated in fae4239

Drafts do trigger CI on travis-ci.com?

They triggered on this WIP draft pull request gitter-lab/SINGE#13 I'm not sure what we did differently there to get it to work.