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
Aspect 1.5 #2190
Aspect 1.5 #2190
Conversation
Hi Felipe - Thanks for finding and pointing out the incorrect documentation! However, I don't see the commit with the changes you describe? Also, would you mind adding the changes from a branch off of the current developer version? This would significantly reduce the number of merge conflicts. If you would like, I can provide some step-by-step instructions on how to do this. If it's easier on your side, also happy to submit a pull request with the fix you outline above. Thanks again! |
Hi @unfelipe, I do not think this pull request is what you intended. You opened a pull request from the main release branch |
@gassmoeller - Thanks for closing this, was going to do so today. @unfelipe and I have been discussing offline about how to do a pull request. |
Wow, this PR demonstrates an absolutely dangerous feature of github. To all developers with write access to the repository who see this: Do not press the 'Delete branch' button when somebody opens a pull request from the main repo to the main repo. You might delete a branch we want to keep (like the 1.5 release branch in this case). While it is fixable (the release tag will stay around), it will cause some trouble. I did not know this would be offered by Github. |
Yikes. Also surprised that option is offered as a feature in pull requests, especially from users without write access. |
How interesting -- that's about as insidious as phishing attacks with forged web sites! |
@tjesser-ucdavis-edu had the proposal to just make every release branch a protected branch. Maybe that would remove the button, something to try. |
Hi all,
warm regards,
Felipe