-
Notifications
You must be signed in to change notification settings - Fork 33
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
Tag a release #191
Comments
I want to have this Windows fix #188, merged before new tag. Although, it's already checked and ready to merge. |
For me it would make sense to add #194 before tagging a new version. I would also like to see #179 and #184 get merged for the next release. What do you think @TotalVerb, @Michael-Klassen and @tonyhffong? |
Releases are cheap... |
@tonyhffong, perhaps it would be a good idea to enable attobot on this repository. |
We need to first merge #194 before tagging, as that includes an important change to REQUIRE. |
I'm supporting the idea of attobot. I have used it one time and it made the registration to METADATA really easy. Even committing changes to the pull request was easy, you just need to delete both the release and the tag separately and then recreate the release in Github. |
Attobot definitely makes this easier, but since Tony is the owner of this repository, he is the only one who can enable it. |
For use with the
linter-julia
Atom plugin.The text was updated successfully, but these errors were encountered: