We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Parent Epic: #207
While working on I should see a pill that shows how many stars a GitHub resource has with the specified styling #101 we found that one of the repos has been handed over to a different owner, that makes us create a request to get the stars of repo "X" and getting the stars for the new repo "Y".
Since we are creating bulk requests to github, we are unable to know which is the changed repo.
When this happens, the whole application fails to start.
the solution we came up with is to create a sanity check job that makes sure that no repos of the current resources has been moved.
We can also add to it more tasks to check the existence of the container image and the repo
that job could be run periodically and be a prerequisite to deploying to prod.
The text was updated successfully, but these errors were encountered:
Successfully merging a pull request may close this issue.
Parent Epic: #207
While working on I should see a pill that shows how many stars a GitHub resource has with the specified styling #101 we found that one of the repos has been handed over to a different owner, that makes us create a request to get the stars of repo "X" and getting the stars for the new repo "Y".
Since we are creating bulk requests to github, we are unable to know which is the changed repo.
When this happens, the whole application fails to start.
the solution we came up with is to create a sanity check job that makes sure that no repos of the current resources has been moved.
We can also add to it more tasks to check the existence of the container image and the repo
that job could be run periodically and be a prerequisite to deploying to prod.
The text was updated successfully, but these errors were encountered: