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

Fixed exception when encountering empty GitHub repo #593

Closed
wants to merge 2 commits into from

Conversation

tsunez
Copy link
Collaborator

@tsunez tsunez commented Oct 6, 2023

Also removed GitHub actions from the forked repo because its missing environment variables to run correctly.

By submitting a PR to this repository, you agree to the terms within the Checkmarx Code of Conduct. Please see the contributing guidelines for how to create and submit a high-quality PR for this repo.

Description

Describe the purpose of this PR along with any background information and the impacts of the proposed change.

References

Include supporting link to GitHub Issue/PR number

Testing

Describe how this change was tested. Be specific about anything not tested and reasons why. If this solution has unit and/or integration testing, tests should be added for new functionality and existing tests should complete without errors.

Please include any manual steps for testing end-to-end or functionality not covered by unit/integration tests.

Checklist

  • I have added documentation for new/changed functionality in this PR (if applicable).
  • I have updated the CLI help for new/changed functionality in this PR (if applicable).
  • All active GitHub checks for tests, formatting, and security are passing
  • The correct base branch is being used

…tributors. Also removed GitHub actions from the forked repo because its missing environment variables to run correctly.
@pedrompflopes pedrompflopes requested review from a team, margaritalm and hmmachadocx and removed request for a team October 6, 2023 19:21
was coming back it was failing do the wait/retry process. This caused an
issue when the GitHub API rate limit was exceeded, the delay process
should have provided 1 minute cooldown. The code now specifically test
the response code and only proceedes when 200 is found. This seems to
correct the problem but it has limited testing.
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