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.

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

Prevent accidental analysis of the get-pip.py script. #349

Merged
merged 1 commit into from
Dec 22, 2020

Conversation

chrisgavin
Copy link
Contributor

It seems like in some cases this script gets analyzed. We can either remove it after running it, or just not save it at all.

Merge / deployment checklist

  • Confirm this change is backwards compatible with existing workflows.
  • Confirm the readme has been updated if necessary.

@chrisgavin
Copy link
Contributor Author

chrisgavin commented Dec 22, 2020

I've verified that this does fix the extraction of get-pip.py. The Action previously output these lines which are gone when running it with this branch:

  [2020-12-22 14:31:21] [build] [INFO] [2] Extracted file /home/runner/work/py2004/py2004/get-pip.py in 774ms
  [2020-12-22 14:31:21] [build] [INFO] [2] Extracted file /home/runner/work/py2004/py2004/get-pip.py in 774ms

(Also a bunch of other imports of get-pip.py are no longer extracted too! 🎉)

@chrisgavin chrisgavin merged commit 094554c into main Dec 22, 2020
@chrisgavin chrisgavin deleted the prevent-accidental-analysis-of-get-pip branch December 22, 2020 14:48
@github-actions github-actions bot mentioned this pull request Dec 28, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants