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 package F1Method: 0.1.0 #571

Merged
merged 1 commit into from
May 6, 2019
Merged

Conversation

JuliaRegistrator
Copy link
Contributor

@JuliaRegistrator JuliaRegistrator commented May 6, 2019

Registering: F1Method
Repository: https://github.com/briochemc/F1Method.jl
Version: v0.1.0
Commit: 7e7a8997f58b141c8469bd4f32728f6cdb68eaca
Proposed by: @briochemc
Reviewed by: @briochemc
Reference: briochemc/F1Method.jl@7e7a899#commitcomment-33420593

JuliaRegistrator referenced this pull request in briochemc/F1Method.jl May 6, 2019
@fredrikekre
Copy link
Member

Can you add a [compat] section?

@briochemc
Copy link
Contributor

I just added the following to the Project.toml file and pushed the commit:

[compat]
julia = "1.0"

Should I do something else? (I don't see the change here so I'm not sure...)

@fredrikekre
Copy link
Member

retrigger the bot

UUID: d5605bae-6d76-11e9-2fd7-71bcf42edbaa
Repo: https://github.com/briochemc/F1Method.jl.git
Tree: d6bc1b96cc8b72deab796a7bf6f50ef92cc702dc

Registrator tree SHA: dc2928e141674bda1fd68da4c4d9755ee4d2c726
JuliaRegistrator referenced this pull request in briochemc/F1Method.jl May 6, 2019
@fredrikekre fredrikekre merged commit d87c8fe into master May 6, 2019
@julia-tagbot
Copy link

julia-tagbot bot commented May 6, 2019

I tried to create a release but ran into this error:

POST https://api.github.com/repos/briochemc/F1Method.jl/releases: 422 Validation Failed [{Resource:Release Field:tag_name Code:already_exists Message:}]

To retry, comment on this PR with the phrase TagBot tag.
cc: @christopher-dG

@fredrikekre fredrikekre deleted the register/F1Method/v0.1.0 branch May 6, 2019 07:48
@briochemc
Copy link
Contributor

Oh I guess I should not have made a GitHub release myself, sorry! What should I do to correct this? Trigger registrator once more?

@fredrikekre
Copy link
Member

If your own tag is for the right commit its fine.

@briochemc
Copy link
Contributor

Yes it was, but I'll push a new one because I messed up the docs and I want to update them too.
Thanks! (Paper and package announcement coming soon!)

@fredrikekre
Copy link
Member

fredrikekre commented May 6, 2019

You can just remove the release from your repo and comment on this PR and tagbot will make the release, see last section here: https://github.com/apps/julia-tagbot

Edit: Oh, you made other changes too.

@briochemc
Copy link
Contributor

Yes! I think it should be good now :) Thanks again!

@fredrikekre
Copy link
Member

Btw, the release you created yourself points to the wrong commit compared to the updated one here. You probably want to recreate that one, and make it point to 7e7a8997f58b141c8469bd4f32728f6cdb68eaca (or use TagBot).

@briochemc
Copy link
Contributor

Oh! Sorry, I thought having a new one would just be good enough. Could you explain how I can do that with TagBot?

@fredrikekre
Copy link
Member

Delete this https://github.com/briochemc/F1Method.jl/releases/tag/v0.1.0 release and the corresponding tag and then do as described in the link above.

@briochemc
Copy link
Contributor

TagBot tag

@julia-tagbot
Copy link

julia-tagbot bot commented May 6, 2019

I've created release v0.1.0, here it is.

@briochemc
Copy link
Contributor

Yay! 🎉

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.

3 participants