-
Notifications
You must be signed in to change notification settings - Fork 331
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
Merger develop into feature/gravy_valet_intergration #10835
Open
adlius
wants to merge
60
commits into
feature/gravy_valet_integration
Choose a base branch
from
develop
base: feature/gravy_valet_integration
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
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
* Fix admin confirmation link generation and handling * Fix test failures * Refactor confirmation link logic and add unit tests * cleanup unused code --------- Co-authored-by: Uditi Mehta <uditimehta@coss-mbp.myfiosgateway.com> Co-authored-by: Uditi Mehta <uditimehta@COSs-MBP.lan>
Resolve issue with updating preprint fields and validation errors * [ENG-6242] #10758
[ENG-6195] Fix admin confirmation link generation and handling #10734
[ENG-5242]
add `--also-decatalog` param to decatalog all deleted/private items
* add management command to migrate preprint affiliations * make sure migrations uses primary instead of replica, improve tests * remove redundant permission --------- Co-authored-by: John Tordoff <>
* Add OOPSpam and Akismet metrics to spam report * Add spam/ham metrics for OOPSpam and Akismet with FK join fix, test cleanup * Add private spam metrics report with preprint inclusion * Validate category; add PrivateSpamMetricsReporter to monthly reports --------- Co-authored-by: Uditi Mehta <uditimehta@COSs-MBP.lan>
prevent counted-usages with different `action_labels` from overwriting each other -- deduplicate only when `action_labels` match exactly
- update monthly reporters with `iter_report_kwargs` (mostly affects `PublicItemUsageReporter`, which was badly optimized to generate many reports at once) - add `schedule_monthly_reporter` task that schedules tasks from `iter_report_kwargs` results - change `MonthlyReporter.followup_task()` to run per-report
…d-update [ENG-6685] B&I Release Fixes
B&I Release - Migrate Preprint Affilations - Add OOPSpam and Akismet metrics to spam report - Add PrivateSpamMetricsReport - Update PrivateSpamMetricsReporter to work with refactored MonthlyReporter - Fix duplicate reports when run for past years - Fix counted-usage clobbers
Co-authored-by: abram axel booth <boothaa@gmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Purpose
Changes
QA Notes
Please make verification statements inspired by your code and what your code touches.
What are the areas of risk?
Any concerns/considerations/questions that development raised?
Documentation
Side Effects
Ticket