
@ben is there a reason you don’t merge commits in a way that shows up as a merge on github?

@samth I’m not sure what you mean. (1) I want to avoid merge commits (2) I prefer pulling the commit onto my master and testing a little instead of clicking the “squash and merge” button"

@ben If you rebase your local branch, then force push to update the remote branch before pushing the commit to master, then GH will mark the PR as merged automatically.

should I always do that? its hard to do if the remote branch isn’t mine

You can often push to the remote branch even if it isn’t yours, because by default GH grants push access to a branch used to submit a PR.

(This is a little-known feature, and my guess is that many contributors don’t actually know they’ve done this, but it’s what the “Allow edits from maintainers” checkbox means in the PR sidebar.)

@ben I think “do testing locally and then click the button” seems like a reasonable approach

ok

@mflatt In case you aren’t aware of it: https://github.com/racket/pict/issues/42

It looks like its related to us updating cairo/pango, but when using pdf-dc% directly the issue goes away.

Nothing much. Documentation mostly.

Thanks - I’ve seen. I’m just several tasks away from being able to do anything about it right now.

right

I’ll see if I can contribute

that would be great

I’ve renamed a Scribble file documenting a package, and now I’m getting warnings from raco setup
of the form: “WARNING: duplicate tag: [some tag] in: <unknown> in: [the document I just renamed]”. Is there a cache somewhere that I need to delete? I’m already using the --doc-index
flag for raco setup
.

@peter has joined the channel

@dan.ml.901 has joined the channel

I’m using raco setup
on a local collection and it’s ignoring a .scrbl
file I have in the collection. How can I get it to pick it up and generate the docs?

i’m guessing i just need some reality check

@dan.ml.901 Have you listed the file under the scribblings
key in an info.rkt
file?

yes

Also, is this a multi-collection package? (That’s a problem someone else had.)

no… it’s pretty simple


That looks right. Something else you might check is if the package is installed in user-specific or installation-wide scope: if it is user-specific, it won’t show up on the installation-wide listing. (That has thrown me off sometimes.) You could also try adding the --doc-index
flag to raco setup
.

hmm it’s not installed at all, that’s probably it

yeah that was it

Is anybody aware of an exporter of rackunit test results as a JUnit compatible XML file?