TagBot trigger issue - Githubissues

JuliaTagBot commented 1 year ago

This issue is used to trigger TagBot; feel free to unsubscribe.

If you haven't already, you should update your TagBot.yml to include issue comment triggers. Please see this post on Discourse for instructions and more details.

If you'd like for me to do this for you, comment TagBot fix on this issue. I'll open a PR within a few hours, please be patient!

JuliaTagBot commented 1 year ago

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/81682

JuliaTagBot commented 1 year ago

Triggering TagBot for merged registry pull request

This extra notification is being sent because I expected a tag to exist by now, but it doesn't. You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

JuliaTagBot commented 1 year ago

Triggering TagBot for merged registry pull request

This extra notification is being sent because I expected a tag to exist by now, but it doesn't. You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

JuliaTagBot commented 1 year ago

Triggering TagBot for merged registry pull request

This extra notification is being sent because I expected a tag to exist by now, but it doesn't. You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

JuliaTagBot commented 1 year ago

Triggering TagBot for merged registry pull request

This extra notification is being sent because I expected a tag to exist by now, but it doesn't. You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

JuliaTagBot commented 1 year ago

Triggering TagBot for merged registry pull request

This extra notification is being sent because I expected a tag to exist by now, but it doesn't. You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

JuliaTagBot commented 1 year ago

Triggering TagBot for merged registry pull request

This extra notification is being sent because I expected a tag to exist by now, but it doesn't. You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

JuliaTagBot commented 1 year ago

Triggering TagBot for merged registry pull request

This extra notification is being sent because I expected a tag to exist by now, but it doesn't. You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

JuliaTagBot commented 1 year ago

Triggering TagBot for merged registry pull request

This extra notification is being sent because I expected a tag to exist by now, but it doesn't. You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

JuliaTagBot commented 1 year ago

Triggering TagBot for merged registry pull request

This extra notification is being sent because I expected a tag to exist by now, but it doesn't. You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

JuliaTagBot commented 1 year ago

Triggering TagBot for merged registry pull request

This extra notification is being sent because I expected a tag to exist by now, but it doesn't. You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

JuliaTagBot commented 1 year ago

Triggering TagBot for merged registry pull request

This extra notification is being sent because I expected a tag to exist by now, but it doesn't. You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

JuliaTagBot commented 1 year ago

Triggering TagBot for merged registry pull request

This extra notification is being sent because I expected a tag to exist by now, but it doesn't. You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

JuliaTagBot commented 1 year ago

Triggering TagBot for merged registry pull request

This extra notification is being sent because I expected a tag to exist by now, but it doesn't. You may want to check your TagBot configuration to ensure that it's running, and if it is, check the logs to make sure that there are no errors.

brendanjohnharris commented 1 year ago

TagBot fix

brendanjohnharris commented 1 year ago

@JuliaRegistrator register

JuliaRegistrator commented 1 year ago

Error while trying to register: "Tag with name v0.2.0 already exists and points to a different commit"

brendanjohnharris commented 1 year ago

@JuliaRegistrator register

JuliaRegistrator commented 1 year ago

Error while trying to register: "Tag with name v0.2.0 already exists and points to a different commit"

brendanjohnharris commented 1 year ago

@JuliaRegistrator register

JuliaRegistrator commented 1 year ago

Error while trying to register: "Tag with name v0.2.0 already exists and points to a different commit"

brendanjohnharris commented 1 year ago

@JuliaRegistrator register

JuliaRegistrator commented 1 year ago

Registration pull request created: JuliaRegistries/General/84064

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.2.0 -m "<description of version>" 831654581ba648ab69146cc55f03dbdc63e82d5e
git push origin v0.2.0

brendanjohnharris commented 1 year ago

@JuliaRegistrator register

JuliaRegistrator commented 1 year ago

Registration pull request created: JuliaRegistries/General/84806

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

Also, note the warning: Version 0.4.0 skips over 0.2.0 This can be safely ignored. However, if you want to fix this you can do so. Call register() again after making the fix. This will update the Pull request.

brendanjohnharris commented 1 year ago

@JuliaRegistrator register

JuliaRegistrator commented 1 year ago

Registration pull request created: JuliaRegistries/General/84807

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

Also, note the warning: Version 0.3.0 skips over 0.2.0 This can be safely ignored. However, if you want to fix this you can do so. Call register() again after making the fix. This will update the Pull request.

brendanjohnharris commented 1 year ago

@JuliaRegistrator register

JuliaRegistrator commented 1 year ago

Registration pull request updated: JuliaRegistries/General/84807

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.3.0 -m "<description of version>" 63ecb0e792ddd659c8825c542494c90eb4f6c1e1
git push origin v0.3.0

Also, note the warning: Version 0.3.0 skips over 0.2.0 This can be safely ignored. However, if you want to fix this you can do so. Call register() again after making the fix. This will update the Pull request.

brendanjohnharris commented 1 year ago

@JuliaRegistrator register

JuliaRegistrator commented 1 year ago

Registration pull request updated: JuliaRegistries/General/84064

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

brendanjohnharris commented 10 months ago

@JuliaRegistrator register

JuliaRegistrator commented 10 months ago

Registration pull request created: JuliaRegistries/General/89813

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.2.1 -m "<description of version>" 90a92eae22434dadd3fc735f7bbed98579cace87
git push origin v0.2.1

JuliaRegistrator commented 10 months ago

Registration pull request created: JuliaRegistries/General/90132

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.2.3 -m "<description of version>" 3e899bf3bc9080fafb5c9e268795e4f90e388312
git push origin v0.2.3

Also, note the warning: Version 0.2.3 skips over 0.2.2 This can be safely ignored. However, if you want to fix this you can do so. Call register() again after making the fix. This will update the Pull request.

JuliaRegistrator commented 10 months ago

Registration pull request updated: JuliaRegistries/General/90132

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.2.3 -m "<description of version>" 3e899bf3bc9080fafb5c9e268795e4f90e388312
git push origin v0.2.3

Also, note the warning: Version 0.2.3 skips over 0.2.2 This can be safely ignored. However, if you want to fix this you can do so. Call register() again after making the fix. This will update the Pull request.

brendanjohnharris commented 10 months ago

@JuliaRegistrator register

JuliaRegistrator commented 10 months ago

Registration pull request created: JuliaRegistries/General/90133

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.2.2 -m "<description of version>" 9f742e01e08b2c7a7df812bf868252445cafcbcf
git push origin v0.2.2

brendanjohnharris commented 7 months ago

@JuliaRegistrator register

JuliaRegistrator commented 7 months ago

Registration pull request created: JuliaRegistries/General/95350

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

brendanjohnharris commented 7 months ago

@JuliaRegistrator register

Release notes:

Add spike train functionality and spike-train power spectra

JuliaRegistrator commented 7 months ago

Registration pull request updated: JuliaRegistries/General/95350

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

brendanjohnharris commented 7 months ago

@JuliaRegistrator register

JuliaRegistrator commented 7 months ago

Registration pull request created: JuliaRegistries/General/96206

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.2.4 -m "<description of version>" 21dc2e37a9cbf4fe7c4d292541dea1521e852ec2
git push origin v0.2.4

brendanjohnharris commented 7 months ago

@JuliaRegistrator register

JuliaRegistrator commented 7 months ago

Registration pull request created: JuliaRegistries/General/96216

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.2.5 -m "<description of version>" 3b7d36d2ccf4c314805b41ef5038ae5aa2e0cb1e
git push origin v0.2.5

brendanjohnharris commented 5 months ago

@JuliaRegistrator register

Release notes:

Circular statistcs
Multidimensional time series
Additional pre-defined filters (lowpass, highpass)
Rectification and joint rectification
Instantaneous frequency, analytic phase and amplitude
Peak detection for spectra
Padding for spectra
Wavelets
Basic spike train dependency measures, and types for spike trains
Spike-train surrogates
Update for new Makie version

JuliaRegistrator commented 5 months ago

Registration pull request created: JuliaRegistries/General/99664

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.3.0 -m "<description of version>" 8bde5f80271e389ad87a535b66f9ef7b1c0b850c
git push origin v0.3.0

brendanjohnharris / TimeseriesTools.jl

TagBot trigger issue #2

Tip: Release Notes

Tagging

Tagging

Tip: Release Notes

Tagging

Tip: Release Notes

Tagging

Tagging