We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
We need to formally release 0.8. @Silvyre has volunteered to do this, and I'll help him.
I'm thinking to use 382aba4 as our commit. Take a look at https://github.com/Seneca-CDOT/telescope/commits/master?before=c5be1b508491b59ea0db9efdbd9037382ca7cbfb+35 and see if there is a more logical one to use.
We're planning to do this mid-afternoon today on Slack, so please let me know if you have a different commit you want used for 0.8.
The text was updated successfully, but these errors were encountered:
This is done, but I'll leave it open while we sort out what happened in release-it/release-it#632
Sorry, something went wrong.
Fix Seneca-CDOT#880: add pushRepo to github release step in release-i…
8d80cd1
…t, update version.
Fix #880: add pushRepo to github release step in release-it, update v…
83f701c
…ersion.
humphd
Successfully merging a pull request may close this issue.
We need to formally release 0.8. @Silvyre has volunteered to do this, and I'll help him.
I'm thinking to use 382aba4 as our commit. Take a look at https://github.com/Seneca-CDOT/telescope/commits/master?before=c5be1b508491b59ea0db9efdbd9037382ca7cbfb+35 and see if there is a more logical one to use.
We're planning to do this mid-afternoon today on Slack, so please let me know if you have a different commit you want used for 0.8.
The text was updated successfully, but these errors were encountered: