-
Notifications
You must be signed in to change notification settings - Fork 600
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
chore: rename java -> legacy #1526
Conversation
Will fix doc links later -- handling too many changes is too hard for me. |
Also all Java checks are disabled -- will add back later. |
3b061c7
to
5905aa1
Compare
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.
A big step!
5905aa1
to
47ca84d
Compare
47ca84d
to
6c9c126
Compare
Codecov Report
@@ Coverage Diff @@
## main #1526 +/- ##
=========================================
Coverage 70.14% 70.14%
Complexity 2766 2766
=========================================
Files 1031 1031
Lines 90546 90546
Branches 1790 1790
=========================================
+ Hits 63514 63516 +2
+ Misses 26141 26139 -2
Partials 891 891
Flags with carried forward coverage won't be shown. Click here to find out more.
📣 Codecov can now indicate which changes are the most critical in Pull Requests. Learn more |
What's changed and what's your intention?
Renaming involves too many changes, so I'd do this in two parts. As no one is currently modifying java path, let's rename it first.
Checklist
Refer to a related PR or issue link (optional)
ref #1092