-
-
Notifications
You must be signed in to change notification settings - Fork 213
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
delete Matric Vector multiply rules that are now in ChainRules #828
Merged
Merged
Changes from all commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
really we should avoid this, open PRs will continuously have conflicts with master, really annoying
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🤷 Its just not that big a deal.
it takes 30 seconds to rebase.
The person it annoys is the PR author, and that is me.
And I am not annoyed.
If other people don't want to rebase to deal with it then they don't have to bump the version number in the PR.
I am not here telling anyone else to.
On a small PR like this one the expectation is that it would be merged quickly (and this would have been except I was on leave and this PR was made before registry had the new version and so CI needed to be retriggered.).
and in a big PR the time to rebase because the version number has changed is nothing compared to the time taken to create the PR.
Further more, rebasing pulls in the changes from master.
And it is possible to end-up with a senario that has two PRs can both pass tests on their own, but not pass tests if merged one after the other.
Rebasing prevents that.
Some CI (definately Bors, idk about our github actions) also prevent that by testing on the result of the merge, rather than testing the actual code in the branch. Still for local tests it is nice the have rebased.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I agree, just making sure we don't force this habit on contributors