-
Notifications
You must be signed in to change notification settings - Fork 380
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
git tag releases #70
Comments
eep I don't want to force push to master :\ I'm happy to start them moving foward though. Is there a good way to backfill? I'm not sure which point in code the revisions were cut. |
I guessed not!!! :-) The only way i can see is adjusting the commits (aka force push) which is a no go! The only pointer really is that most of the docs (your blog & example phoenix_guardian) are relating to 0.6 Perhaps i could help updating the phoenix_guardian to be 0.8.0 ? |
Hey again! |
I'm actually in the process of updating phoenix_guardian atm! I can push up to a branch what I have so far if you want to hack on it too :) If you think we can get to releases from where we are then cool but please don't break anything :| How can I help? |
Hey,
Would it be possible to git-tag the version bumps in the future?
I'm happy to do the grunt work and find the previous commit ids if backward tags can be done by you? (Guessing it requires force push of master, so not repo friendly to do!) but the offer is there!
The text was updated successfully, but these errors were encountered: