Andrew Williamson

using ContentActionDeleteCollection would need us to start on https://mozilla-hub.atlassian.net/browse/AOP-460 - the major pieces of work are: - the ability to select a policy and/or notes to justify the takedown when...

> @eviljeff has anything changed in the API by chance? Not that I'm aware of, but I've not worked on any changes to the API in quite a while.

According to the changelog there hasn't been a change this year - (there's an upcoming change that will land on prod next week). I can't state for certain the changelog...

I think this may be [another](https://github.com/mozilla/web-ext/issues/3446) case of the docs stating the wrong environment variable. According to the [source](https://github.com/mozilla/web-ext/blob/master/src/program.js#L567) the arg is `upload-source-code`, so the environment variable would be `WEB_EXT_UPLOAD_SOURCE_CODE`...

> [@eviljeff](https://github.com/eviljeff) what's the best way of checking the documentation doesn't have any more of these incorrectly stated environment variables? The only way I can think of - and it's...

> To provide an update on my end, as seen with the linked pull request from last week, I made a change with the fix but we are waiting for...

@wagnerand what are your thoughts about this scenario and what the messaging should be? The scenario is an add-on version is rejected and the developer appeals, but also uploads a...

> Do you mean "incorrect"? yes

The workaround would be adding something to the reviewer tools forms to allow the reviewer to choose exactly how the job should be resolved - so they could choose to...

@abyrne-moz unfortunately not - it leverages a function that currently doesn't result in any action (commenting). It still won't let a reviewer take two different actions (a version approval +...