New package: Harbor v1.0.0

[JuliaRegistrator]

• Registering package: Harbor
• Repository: https://github.com/JuliaServices/Harbor.jl
• Created by: @quinnj
• Version: v1.0.0
• Commit: 7c82e624f1ac798dd41a6e6cb73fefe164c68c1d
• Reviewed by: @quinnj
• Reference: JuliaServices/Harbor.jl@7c82e62#commitcomment-153761647

[github-actions]

Hello, I am an automated registration bot. I help manage the registration process by checking your registration against a set of AutoMerge guidelines. If all these guidelines are met, this pull request will be merged automatically, completing your registration. It is strongly recommended to follow the guidelines, since otherwise the pull request needs to be manually reviewed and merged by a human.

1. New package registration

Please make sure that you have read the package naming guidelines.

2. AutoMerge Guidelines are all met! ✅

Your new package registration met all of the guidelines for auto-merging and is scheduled to be merged when the mandatory waiting period (3 days) has elapsed.

3. To pause or stop registration

If you want to prevent this pull request from being auto-merged, simply leave a comment. If you want to post a comment without blocking auto-merging, you must include the text [noblock] in your comment.

Tip: You can edit blocking comments to add [noblock] in order to unblock auto-merging.

[goerz]

It seems that the links to the documentation are currently broken. For a v1.0.0 initial release, it would be especially important that the documentation is complete, as you're indicating (assuming you're following SemVer) that the package has a stable API.

I would also consider extending the "Usage" documentation in the README a little, although this might become redundant with proper full documentation.

[noblock]

[quinnj]

[noblock] Good catch @goerz, I had finally got the Documentation CI job to run successfully and it said it deployed, but I failed to actually check that the docs were published. Turns out I had to enable github pages in my repo settings. That's fixed now. I'll update the README.md as well, but I dont' believe any additional commits are required to update this registration

(you'll have to edit your comment to add [noblock] if your concerns are satisfied)

[goerz]

Yup, all good! Thanks for fixing the documentation! [noblock]