Register in General

[mpf]

@JuliaRegistrator register()

[JuliaRegistrator]

Error while trying to register: Register Failed @mpf, it looks like you are not a publicly listed member/owner in the parent organization (MPF-Optimization-Laboratory). If you are a member/owner, you will need to change your membership to public. See GitHub Help

[mpf]

@JuliaRegistrator register()

[JuliaRegistrator]

Registration pull request created: JuliaRegistries/General/111419

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.0.1 -m "<description of version>" f6a0552f2fa81ff9eee29774b445a7a564f9aade
git push origin v0.0.1

[JuliaRegistrator]

Registration pull request updated: JuliaRegistries/General/111419

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.0.1 -m "<description of version>" f6a0552f2fa81ff9eee29774b445a7a564f9aade
git push origin v0.0.1

[mpf]

@JuliaRegistrator register

Release notes:

Initial release of the Julia port of the original Matlab Active Set Pursuit implementation.

[JuliaRegistrator]

Registration pull request updated: JuliaRegistries/General/111419

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.0.1 -m "<description of version>" f6a0552f2fa81ff9eee29774b445a7a564f9aade
git push origin v0.0.1

[JuliaRegistrator]

Registration pull request updated: JuliaRegistries/General/111419

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.0.1 -m "<description of version>" f6a0552f2fa81ff9eee29774b445a7a564f9aade
git push origin v0.0.1

[cortner]

@JuliaRegistrator register

[JuliaRegistrator]

Registration pull request created: JuliaRegistries/General/114110

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.0.2 -m "<description of version>" 521eb90442d1b97504e2c3c5d1e129ef710306cb
git push origin v0.0.2