Add Github dep for new cred support if used

[thedoubl3j]

fixed git requirements file with new line so dep compiler can run and added new github dep and relevant deps it needs

SUMMARY

ISSUE TYPE

• Bug, Docs Fix or other nominal change

COMPONENT NAME

• Other

AWX VERSION

devel

ADDITIONAL INFORMATION

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 77.88%. Comparing base (bf4d454) to head (5d167b6).
Report is 1 commits behind head on devel.

✅ All tests successful. No failed tests found.

[AlanCoding]

API test failure

Exception: Included licenses not consistent with requirements:
 license for requirement pygithub is missing
 license for requirement pynacl is missing

[AlanCoding]

Seems that the schema reference got blown away.

2025-02-20T20:26:59.1446957Z diff -u -b reference-schema.json schema.json
2025-02-20T20:26:59.2183079Z --- reference-schema.json	2025-02-20 20:26:59.140367865 +0000
2025-02-20T20:26:59.2183769Z +++ schema.json	2025-02-20 20:26:49.290396558 +0000
2025-02-20T20:26:59.2184236Z @@ -1,2 +1,41679 @@
2025-02-20T20:26:59.2184606Z -<?xml version="1.0" encoding="UTF-8"?>
2025-02-20T20:26:59.2186511Z -<Error><Code>NoSuchKey</Code><Message>The specified key does not exist.</Message><Key>devel/schema.json</Key><RequestId>D74G2SX3Z70CD6HQ</RequestId><HostId>6pT9m7AKYF7uj29ilNsaSP1OLhR0gImp8Q/vUZGAHjcmEhe7nFXujEya5wcZm944+5+AbDLhnmU=</HostId></Error>

For right now, I wouldn't worry about it much. The api-schema check.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[webknjaz]

@thedoubl3j it's 2.6.1 in awx-plugins

[webknjaz]

@thedoubl3j it's a transitive dep. Isn't this file supposed to list direct deps? The correct thing to do would be to depend on awx-plugins-core [credentials-github-app] that declares the dependency.

[AlanCoding]

You are correct. Put up #15853

I was a bit panicked to merge this PR yesterday, because it was breaking checks and presumably the installs. If we have an outright missing dependency, I'd hope that we could ignore all checks and force it through. After that, fine to do cleanup.

The way this is a floating dependency on awx-plugins-core, honestly, our best-case scenario would have been to add it to requirements.in a day before merging the plugins patch. Then merge the plugins patch, then update the requirements. Otherwise - pin the plugins version.