Skip to content

New package: BeForData v0.3.8#142637

Closed
JuliaRegistrator wants to merge 1 commit intomasterfrom
registrator-befordata-49581401-v0.3.8-47e2317db1
Closed

New package: BeForData v0.3.8#142637
JuliaRegistrator wants to merge 1 commit intomasterfrom
registrator-befordata-49581401-v0.3.8-47e2317db1

Conversation

@JuliaRegistrator
Copy link
Contributor

UUID: 49581401-e3b0-43cb-bb9c-49750952130d
Repo: https://github.com/lindemann09/BeForData.jl.git
Tree: 2db9d9a528ab69d0130b2f9747382c89f792a1d0

Registrator tree SHA: 50f504d641745716a5b3eabaf681d3a4937d2ae3
@github-actions
Copy link
Contributor

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
Copy link
Member

goerz commented Nov 17, 2025

Thank you for submitting your package! Could you add a little bit of documentation before registering? At the very least, that would be a small usage example in the README. An important part of packages in General is that any potential user can figure out what the package is about and how to get started with using it. That is really difficult when there is no documentation.

In the longer term, I definitely recommend setting up a Documenter-based documentation. Before a v1.0 release, or for smaller packages that can be effectively described entirely with their README, that's not a requirement, though.

@JuliaTagBot JuliaTagBot added the AutoMerge: last run blocked by comment PR blocked by one or more comments lacking the string [noblock]. label Nov 17, 2025
@github-actions
Copy link
Contributor

This pull request has been inactive for 30 days and will be automatically closed 7 days from now. If this pull request should not be closed, please either (1) fix the AutoMerge issues and re-trigger Registrator, which will automatically update the pull request, or (2) post a comment explaining why you would like this pull request to be manually merged. [noblock]

@github-actions github-actions bot added the stale label Dec 18, 2025
@github-actions
Copy link
Contributor

This pull request has been inactive for more than 30 days and has automatically been closed. Feel free to register your package or version again once you fix the AutoMerge issues. [noblock]

@github-actions github-actions bot closed this Dec 26, 2025
@github-actions github-actions bot deleted the registrator-befordata-49581401-v0.3.8-47e2317db1 branch December 26, 2025 12:24
@lindemann09
Copy link

I added more documentation and initiated a new registration: see #150921

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

AutoMerge: last run blocked by comment PR blocked by one or more comments lacking the string [noblock]. new package stale

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants