-
Notifications
You must be signed in to change notification settings - Fork 35
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
Fix deprecation warnings #811
Conversation
- name: Install requirements | ||
run: pip3 install github | ||
- name: Check commit message | ||
{{ install_python_deps(["requests", "pygithub"]) | indent(6) }} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We install missing packages in the scripts themselves; the question is, do we need this^?
pip3 install pygithub |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I thought i removed that.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actually, i did.
@@ -74,7 +73,7 @@ jobs: | |||
|
|||
{{ setup_python() | indent(6) }} | |||
|
|||
{{ install_python_deps("requests") | indent(6) }} | |||
{{ install_python_deps(["requests"]) | indent(6) }} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would also install this requirement inside the caller ".github/workflows/scripts/publish_docs.sh". Do you think it is worth it to revisit all installing dependencies and move them to one place?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I intended to stop installing anything from scripts, because i consider that to be dangerous if you try to run any of these locally.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Gotcha, then it makes sense to remove pip calls from the scripts, in another PR.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
And i dind't even check with "git grep" ... XD
{%- if test_lowerbounds %} | ||
echo "{{ "${{ needs.test.outputs.deprecations-lowerbounds }}" }}" | base64 -d | ||
{%- endif %} | ||
cat deprecations-*.txt | sort -u |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we miss "{{ plugin_name }}" in the path?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
At this point no. As we do no checkout, we don't have the directory "{{ plugin_name }}" to do that. Do you think we should create it for consistency?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would say yes.
Consolidate some macros. Add a lot of quoting because explicit is better than implicit. [noissue]
5b6d75a
to
146b9c8
Compare
720f438
to
5f9c44b
Compare
This will not rely on job outputs, but instead use a workflow artifact. [noissue]
[noissue]
5f9c44b
to
b7dd772
Compare
This is yet another legacy of the pulp_file merge.