register package

[gszep]

No description provided.

[gszep]

@JuliaRegistrator register

[JuliaRegistrator]

Registration pull request created: JuliaRegistries/General/38641

After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.

This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:

git tag -a v0.1.0 -m "<description of version>" 569b3cb57c0fd4cd9636b20ae3d528f5489c96fc
git push origin v0.1.0

[gszep]

@JuliaRegistrator register

[JuliaRegistrator]

Registration pull request created: JuliaRegistries/General/38651

After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.

This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:

git tag -a v0.1.0 -m "<description of version>" 192e311c5b33566c13783113cb231ae2e0c7395c
git push origin v0.1.0

[gszep]

@JuliaRegistrator register

[JuliaRegistrator]

Registration pull request created: JuliaRegistries/General/38811

After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.

This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:

git tag -a v0.1.1 -m "<description of version>" 32ae84eb6b1b5fb80398f1e811f64cdf3d11d777
git push origin v0.1.1

[gszep]

@JuliaRegistrator register

[JuliaRegistrator]

Registration pull request created: JuliaRegistries/General/47665

After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.

This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:

git tag -a v0.1.2 -m "<description of version>" 49b1efb0bd73377cfd4d9eea50552fef22f1c7e4
git push origin v0.1.2

[gszep]

@JuliaRegistrator register

[JuliaRegistrator]

Registration pull request created: JuliaRegistries/General/56949

After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.

This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:

git tag -a v0.1.3 -m "<description of version>" fa1e1464c671b2d14551d90d9887b2b0f27d0b3d
git push origin v0.1.3

[gszep]

@JuliaRegistrator register

[JuliaRegistrator]

Registration pull request created: JuliaRegistries/General/107899

Tip: Release Notes

Did you know you can add release notes too? Just add markdown formatted text underneath the comment after the text
"Release notes:" and it will be added to the registry PR, and if TagBot is installed it will also be added to the
release that TagBot creates. i.e.

@JuliaRegistrator register

Release notes:

## Breaking changes

- blah

To add them here just re-invoke and the PR will be updated.

Tagging

After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.

This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:

git tag -a v0.1.4 -m "<description of version>" 90cb6985473e6fb5dac520bf6500ab8cd7ce608b
git push origin v0.1.4

[gszep]

@JuliaRegistrator register

[JuliaRegistrator]

Registration pull request updated: JuliaRegistries/General/107899

Tip: Release Notes

Did you know you can add release notes too? Just add markdown formatted text underneath the comment after the text
"Release notes:" and it will be added to the registry PR, and if TagBot is installed it will also be added to the
release that TagBot creates. i.e.

@JuliaRegistrator register

Release notes:

## Breaking changes

- blah

To add them here just re-invoke and the PR will be updated.

Tagging

After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.

This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:

git tag -a v0.1.4 -m "<description of version>" 534ee7c23af16d542a248f181f5e6be7056e30b6
git push origin v0.1.4

[rveltz]

Hey,

Are you sure you want to do this? BK has changed a lot in the mean time.

please also consider moving it to the gh org bifurcatiokit

[gszep]

Hi @rveltz ! Thank you for reaching out :) well all the of unit tests I created are passing? I would appreciate if you can find any bugs in the diff between the two versions. Happy to move this project to the org you mention. I can initiate the transfer now

[gszep]

I do not have permissions to create repos on the bifurcationkit org. You would have to add me as a member with certain privileges before I can initiate transfer. I would also appreciate retaining admin rights to BifurcationInference.jl 😄

[rveltz]

The diff is massive but I congratulate because that was not simple work. I am impressed

[rveltz]

I would also appreciate retaining admin rights to BifurcationInference.jl

Sure, if I mess up, I will give it back to you :D

[rveltz]

I sent you an invit

[gszep]

I think the diff is only massive because I had an automatic formatter on CTRL+S haha

[rveltz]

Do you have enough rights on the org?

…

On Jun 1, 2024, at 5:37 PM, Grisha Szep ***@***.***> wrote: I think the diff is only massive because I had an automatic formatter on CTRL+S haha — Reply to this email directly, view it on GitHub <#11 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAMEUBGSRIF5CVJR7RFWYSDZFHTFPAVCNFSM46QKFAA2U5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TEMJUGM2DSMBVHAZA>. You are receiving this because you were mentioned.

[rveltz]

Thank you for joining! You have admin rights to your own repo :D I will try to find a better way because you are only collaborator. If you are a member with admin right, you would have admin rights to all repo, I am not sure how to change this granularity

…

On Jun 1, 2024, at 5:43 PM, Romain Veltz ***@***.***> wrote: Do you have enough rights on the org? > On Jun 1, 2024, at 5:37 PM, Grisha Szep ***@***.***> wrote: > > > I think the diff is only massive because I had an automatic formatter on CTRL+S haha > > — > Reply to this email directly, view it on GitHub <#11 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAMEUBGSRIF5CVJR7RFWYSDZFHTFPAVCNFSM46QKFAA2U5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TEMJUGM2DSMBVHAZA>. > You are receiving this because you were mentioned. >