Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Auto upload file for Validation-SmartScreen #1523

Closed
CGQAQ opened this issue Jun 3, 2020 · 3 comments
Closed

Auto upload file for Validation-SmartScreen #1523

CGQAQ opened this issue Jun 3, 2020 · 3 comments
Assignees
@KevinLaMS
Labels
Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work.
Milestone
1.7 Packages

Comments

@CGQAQ
Copy link
Contributor

CGQAQ commented Jun 3, 2020

Description of the new feature/enhancement

When there is Validation-SmartScreen error, auto upload file via robot to https://www.microsoft.com/en-us/wdsi/filesubmission to scan the file, as the download URL already in the yaml config file, should not need human to do it
@CGQAQ CGQAQ added the Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. label Jun 3, 2020
@ghost ghost added the Needs: Triage label Jun 3, 2020
@superusercode
Copy link
Contributor

Definitely a key part of #500

@KevinLaMS KevinLaMS self-assigned this Jun 9, 2020
@KevinLaMS
Copy link
Contributor

We agree. We are investigating improving this process. I am working with the smartscreen team and have quit assigning the packages back to the submitter.

@KevinLaMS
Copy link
Contributor

Greetings, the process has changed, this should no longer be an issue.

@denelon denelon added this to the 1.7 Packages milestone Nov 1, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@KevinLaMS KevinLaMS

Labels
Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work.
Projects
None yet
Milestone
1.7 Packages
Development

No branches or pull requests
4 participants
@KevinLaMS @CGQAQ @superusercode @denelon