[github] Update pip deps (NFC)

[keith]

Summary

Minor dep updates identified in https://github.com/llvm/llvm-project/issues/57907

[keith]

llvm/utils/git/requirements.txt.in

7

No need to pin these since they aren't upgraded in the lock file unless explicitly specified in the pip-compile command

[dblaikie]

Looks like this and ( D135532 ) were sent for review, but then committed before that review was attempted/completed?

Could you please wait for reviews to be completed before submitting code.

If code doesn't need pre-commit review (per the guidelines in the LLVM documentation), it's OK/correct to submit it without review - but the general idea is that if something is sent for review, it's because it needed it, and so submitting without that review is problematic (we don't want to encourage folks to submit stuff because they're frustrated with/waiting too long for review - if they felt it needed review in the first place, delayed code review doesn't change that fact)

[keith]

In D135531#3863681, @dblaikie wrote:

Looks like this and ( D135532 ) were sent for review, but then committed before that review was attempted/completed?

Could you please wait for reviews to be completed before submitting code.

If code doesn't need pre-commit review (per the guidelines in the LLVM documentation), it's OK/correct to submit it without review - but the general idea is that if something is sent for review, it's because it needed it, and so submitting without that review is problematic (we don't want to encourage folks to submit stuff because they're frustrated with/waiting too long for review - if they felt it needed review in the first place, delayed code review doesn't change that fact)

Yep sorry! I should have pushed these instead. For these 2 I did feel like "if someone has a herald rule for this and wants to review that's fine", just because outside of the LLVM repo I generally work in a setting where everything gets review regardless of how trivial, but I get that sending for review and then landing without review sends a mixed signal, so I'll be sure to either land, or wait, in the future.

[dblaikie]

In D135531#3863837, @keith wrote:

In D135531#3863681, @dblaikie wrote:

Looks like this and ( D135532 ) were sent for review, but then committed before that review was attempted/completed?

Could you please wait for reviews to be completed before submitting code.

If code doesn't need pre-commit review (per the guidelines in the LLVM documentation), it's OK/correct to submit it without review - but the general idea is that if something is sent for review, it's because it needed it, and so submitting without that review is problematic (we don't want to encourage folks to submit stuff because they're frustrated with/waiting too long for review - if they felt it needed review in the first place, delayed code review doesn't change that fact)

Yep sorry! I should have pushed these instead. For these 2 I did feel like "if someone has a herald rule for this and wants to review that's fine",

I /think/ Herald rules can also fire for direct commits, if I understand correctly?

just because outside of the LLVM repo I generally work in a setting where everything gets review regardless of how trivial, but I get that sending for review and then landing without review sends a mixed signal, so I'll be sure to either land, or wait, in the future.

Yeah, it's a bit quirky, for sure - maybe one of these days we'll get to something more mainstream like github pull requests, etc.

We'll see - thanks for understanding!

llvm/utils/git/requirements.txt

 #
-# This file is autogenerated by pip-compile with python 3.8
+# This file is autogenerated by pip-compile with python 3.9
 # To update, run:
 #
 #    pip-compile --output-file=requirements.txt requirements.txt.in
 #
-certifi==2021.10.8
+certifi==2022.9.24
     # via requests
-cffi==1.15.0
+cffi==1.15.1
     # via pynacl
-charset-normalizer==2.0.10
+charset-normalizer==2.1.1
     # via requests
 deprecated==1.2.13
     # via pygithub
 gitdb==4.0.9
     # via gitpython
-gitpython==3.1.26
+gitpython==3.1.28
     # via -r requirements.txt.in
-idna==3.3
+idna==3.4
     # via requests
 pycparser==2.21
     # via cffi
 pygithub==1.55
     # via -r requirements.txt.in
-pyjwt==2.3.0
+pyjwt==2.5.0
     # via pygithub
 pynacl==1.5.0
     # via pygithub
-requests==2.27.1
+requests==2.28.1
     # via pygithub
 smmap==5.0.0
     # via gitdb
-urllib3==1.26.8
+urllib3==1.26.12
     # via requests
-wrapt==1.13.3
+wrapt==1.14.1
     # via deprecated

llvm/utils/git/requirements.txt.in

 # Convert this file into a requirements.txt file by running:
 #
 # pip install pip-tools
 # pip-compile -o requirements.txt  requirements.txt.in
 
-PyGithub==1.55
-GitPython==3.1.26
+PyGithub
+GitPython