* Allow adding, viewing information about and deleting soft-blocks in the admin
Like other blocklist operations, it goes through a BlocklistSubmission, which
gains a new "block_type" field to determine what kind of block to apply for
this particular submission.
Note: If a version is already soft-blocked or hard-blocked, that version won't
be selectable when creating a new BlocklistSubmission, even of another type.
Future actions will be added to soften or harden blocks.
* rename utils/CinderAction* to actions/ContentAction*
* CinderDecision to ContentDecison
* Add a basic admin to view ContentDecisions
* Add basic queue to show decisions where action has been held
* Added view attachment link on DevHub in relation to #22640
* lint
* renamed attachment_link to attachment_url
* js attachment_url
* test update
* doc
* test
* dont hardcode test
* lint
* limit queries
* Use correct pk in reverse
* Added pastebin reimplementation on reviewer tools side
* make lint
* Moved attachment upload box to own section (and available for all actions)
* Fixed css for textareas, returned datetime-wrapper
* Missing assignment
* Updated naming for files, limited to .txt and .zip, temporarily updated query number assertion
* added waffle enable-activity-log-attachments for user facing menus;
* testing
* corrected test
* Removed zip allowance
* migration conflict
* test (temp)
* import
* remove git_extraction.py from pr
* ???
* numQueries
* review changes
* lint
* prettier
* review changes
* lol lint
* review comment
* Show all current authors on the review page
* Removed extra style
* Added tests
* ruff formatting
* ruff format
* Changed to use class rather than inline style
* Updated tests, better conditional
* Dotted underline under unlisted authors
* Removed underline, modified conditional, removed sidebar Author
* Extra space
* 300 weight font
* Changed due_date_update to update on blur rather than on change
* Add visual indicator (button) of status of date change
* prettier
* removed extra </li>
* moved inline style to class
* Submit on click rather than onblur
* set due_date_reasons bitmask when setting due_date
* add no_transforms in Version.should_have_due_date
* Only annotate Version qs when nessecary
* refactor to make VersionManager.should_have_due_date efficient
* Add flags for newly exposed reasons for due_date
* get_due_date_reason_qs -> get_due_date_reason_q_objects; add docstring
* exclude has developer reply from needs_human_review_other
* fix linelength that ruff format didn't autofix
* only clear abuse/appeal related NHR for resolving jobs
* Allow some policies to be selectable in reviewer tools
* reset due_date after setting NHR to inactive
* show special flag for nhr from abuse reports in review queue
* refactor NeedsHumanReview REASON constants into Choices
* split single flag into three types of abuse/appeal
* optimize queryset construction
* Simplify socketlabs check for status and messaging when something goes wrong.
* Fix comments
* Add more details and formatting to suppressed email status table.
* Copy fixes and updates
* Update src/olympia/devhub/templates/devhub/verify_email.html
Co-authored-by: Francesco Lodolo <flodolo@mozilla.com>
---------
Co-authored-by: Mozilla Add-ons Robot <addons-dev-automation+github@mozilla.com>
Co-authored-by: Francesco Lodolo <flodolo@mozilla.com>
* feat(): add email_verification property to UserProfile
* feat(users): add useful properties to SuppressedEmailVerification model
* feat(devhub): add email verification flow view logic
* chore(): use date only values for socketlabs recipient search
* replace force disable/enable buttons with actions
* update api docs
* move activity logging back to reviewer tools
* expose enable/disable activity log to developers
* correctly stringify activity log in reviewer tools important changes
* rm unused line
* review fixes
* Harmonize footers across devhub (and frontend pages a bit more)
Changes:
- Copy over fonts from addons-frontend, use Inter everywhere
- Use photon-footer everywhere, adding a light blue margin before
to make the transition less aggressive and match header
- Fix error pages block to align content correctly
- Translate strings in footer
* Limit compatibility for Firefox for Android
- Extensions are either compatible with Fennec or Fenix >= 119.0a1, unless they are recommended/line.
- If they are compatible with Fennec, they strict compatibility is enabled.
* add canned reasons to blocksubmission admin
* build on ReviewActionReason for canned response instead
* Fix reviewers tests that didn't create a complete ReviewActionReason
* in migration default canned_block_reason field to '' for existing records
* change version checkboxes to make it clearer between blocking and already blocked
* wrap blocked and not blocked icon & version string in a span, with title
* track Blocked versions per version
* update api docs
* test fixes
* scanners test fixes
* drop now obsolete create_blockversions command
* address review comments; fix failing tests
* restore warning messages about a version being in a submission or block
* add extra tests + optimizations
* Fix failing blocklist/test_serializers.py test
`white-space: pre-wrap` prevents lines from being broken unless an
explicit line break is in there.
Since the content of these fields are external (user-generated), there
is no guarantee of the line length to be within reasonable bounds.
Rather than stretching the layout, add `word-break: break-word` to allow
the line to be wrapped regardless.
* Lock compatibility information if it came from `gecko_android`
Manifest should be the source of truth for compatibility data for Android when
`gecko_android` if set.
* Remove obsolete compatibility changing code
The only add-ons left with strict compatibility should be langpacks,
and we don't want to continue allowing to dynamically alter their
compatibility via devhub.
* Test fixes
* More extra css/js that can be removed
* Remove unused import
* load version adus in review page xhr
* Add top 10 ADU versions box
* moved ADU block to RH sidebar; made style consistent; reviewers js now runs on documen load
* Show which versions have a due date in reviewer tools
Bonus:
- Change "risk" colors to go from yellow to red
- Move and rename "MAD" flag to avoid confusion with needs human review
- Allow changing due date again once the first change goes through
* Show & Allow removing Unlisted Auto-Approval Extra Delay in review tools
Also refactor how flags are displayed, adding a couple new ones and hiding the ones that are not relevant to the version shown in the review page because of the channel.