Allow configuring name

[dudo]

Addresses #39. This should keep existing behavior if the new annotations aren't added.

I haven't modified, or ran any tests... and it looks like we don't have CI. I'll see what I can do to get my env set up (I prefer keeping everything dockerized, though)

Checklist

• Add functionality
• Verify tests
• Update readme

[aflanagan]

@dudo Dang you're fast! I just opened the repo to start working on this :)

I'll take a look through your PR, and am happy to help as you'd like. I also haven't looked into running the test suite locally, but it should run here via GH actions. I'm not sure why that didn't kick off when you opened that initial PR. I'll take a look at that now.

EDIT: I believe those will run on the next commit here.

[dudo]

Hey @aflanagan! I don't think those test failures are related to my changes. I'll punt to you.

[aflanagan]

@dudo I just added you as a maintainer, could you try opening this PR again with a branch based off of this repo instead of your fork? The failures are due to the following GH Actions policy (which makes sense)

Anyone with collaborator access to this repository can use these secrets and variables for actions. They are not passed to workflows that are triggered by a pull request from a fork.

[dudo]

superseded with #41