Closed dblock closed 7 years ago
@dblock Sure let me handle it. Thanks
@dblock I need to ask you something currently I have 2 remotes:
origin
which points to my forked repo.upstream
which points to your repo.I made the release but rubygems fetched the project from my repo thus my forked origin/master is tagged with the new release. I should have changed the origin to your remote correct? How do we fix this now?
Sorry for the inconvenience caused.
I should remove my forked repo and work completely on dblock/ruby-enum
correct?
When you make a release, do it from the non-forked repo.
It's no big deal, I just did git checkout 00c721da834570e9e3498620d8143dd6e4bcf901
, then git tag v0.7.0
and git push --tags
.
Thanks for doing the release @laertispappas!
You should continue working on your fork though for all code, except for doing the release.
@dblock great thanks for the explanation above.
Lets do a release after #14 is merged. Maybe 0.7.0 since #3 is a pretty big piece of functionality.
@laertispappas care to follow https://github.com/dblock/ruby-enum/blob/master/RELEASING.md then?