Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

New version: DigitalAssetExchangeFormatIO v1.1.1 #114649

Conversation

JuliaRegistrator
Copy link
Contributor

UUID: 43182933-f65b-495a-9e05-4d939cea427d
Repo: https://github.com/Larbino1/DigitalAssetExchangeFormatIO.jl.git
Tree: ef1d9b9f492fad9ac9360d85661922e9b66547ac

Registrator tree SHA: 17aec322677d9b81cdd6b9b9236b09a3f1374c6a
Copy link
Contributor

github-actions bot commented Sep 6, 2024

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. AutoMerge Guidelines are all met! ✅

Your new version registration met all of the guidelines for auto-merging and is scheduled to be merged in the next round.

2. 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.

@github-actions github-actions bot added the stale label Oct 6, 2024
@Larbino1
Copy link

Larbino1 commented Oct 8, 2024

[merge approved]

@JuliaTagBot JuliaTagBot merged commit 146e152 into master Oct 8, 2024
11 checks passed
@JuliaTagBot JuliaTagBot deleted the registrator-digitalassetexchangeformatio-43182933-v1.1.1-99071b92a9 branch October 8, 2024 23:16
@giordano
Copy link
Member

giordano commented Oct 8, 2024

@Larbino1 for the record, there was a merge conflict that I had to resolve manually, but you could have fixed yourself automatically at any point by triggering again registration on the same commit as you did before: that'd automatically update the PR and resolve any conflict. Next time 🙂

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

Successfully merging this pull request may close these issues.

4 participants