-
Notifications
You must be signed in to change notification settings - Fork 113
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
Querying Lite-CI API will stuck git node land
#466
Comments
@mmarchini happy to take it unless you're already on it! |
mmarchini
added a commit
to mmarchini/node-core-utils
that referenced
this issue
Aug 8, 2020
Lite CI is not used anymore, but some PRs got Lite-CI runs after some changes to the bot. node-core-utils Lite-CI parsing is not working though, therefore ncu will fail to land those PRs. Removing Lite-CI checks fix the issue and also reduces complexity. Fix: nodejs#466
mmarchini
added a commit
to mmarchini/node-core-utils
that referenced
this issue
Aug 9, 2020
Lite CI is not used anymore, but some PRs got Lite-CI runs after some changes to the bot. node-core-utils Lite-CI parsing is not working though, therefore ncu will fail to land those PRs. Removing Lite-CI checks fix the issue and also reduces complexity. Fix: nodejs#466
mmarchini
added a commit
that referenced
this issue
Aug 14, 2020
Lite CI is not used anymore, but some PRs got Lite-CI runs after some changes to the bot. node-core-utils Lite-CI parsing is not working though, therefore ncu will fail to land those PRs. Removing Lite-CI checks fix the issue and also reduces complexity. Fix: #466
johnfrench3
pushed a commit
to johnfrench3/core-utils-node
that referenced
this issue
Nov 2, 2022
Lite CI is not used anymore, but some PRs got Lite-CI runs after some changes to the bot. node-core-utils Lite-CI parsing is not working though, therefore ncu will fail to land those PRs. Removing Lite-CI checks fix the issue and also reduces complexity. Fix: nodejs/node-core-utils#466
renawolford6
added a commit
to renawolford6/node-dev-build-core-utils
that referenced
this issue
Nov 10, 2022
Lite CI is not used anymore, but some PRs got Lite-CI runs after some changes to the bot. node-core-utils Lite-CI parsing is not working though, therefore ncu will fail to land those PRs. Removing Lite-CI checks fix the issue and also reduces complexity. Fix: nodejs/node-core-utils#466
Developerarif2
pushed a commit
to Developerarif2/node-core-utils
that referenced
this issue
Jan 27, 2023
Lite CI is not used anymore, but some PRs got Lite-CI runs after some changes to the bot. node-core-utils Lite-CI parsing is not working though, therefore ncu will fail to land those PRs. Removing Lite-CI checks fix the issue and also reduces complexity. Fix: nodejs/node-core-utils#466
gerkai
added a commit
to gerkai/node-core-utils-project-build
that referenced
this issue
Jan 27, 2023
Lite CI is not used anymore, but some PRs got Lite-CI runs after some changes to the bot. node-core-utils Lite-CI parsing is not working though, therefore ncu will fail to land those PRs. Removing Lite-CI checks fix the issue and also reduces complexity. Fix: nodejs/node-core-utils#466
shovon58
pushed a commit
to shovon58/node-core-utils
that referenced
this issue
Jun 9, 2023
Lite CI is not used anymore, but some PRs got Lite-CI runs after some changes to the bot. node-core-utils Lite-CI parsing is not working though, therefore ncu will fail to land those PRs. Removing Lite-CI checks fix the issue and also reduces complexity. Fix: nodejs/node-core-utils#466
patrickm68
added a commit
to patrickm68/NodeJS-core-utils
that referenced
this issue
Sep 14, 2023
Lite CI is not used anymore, but some PRs got Lite-CI runs after some changes to the bot. node-core-utils Lite-CI parsing is not working though, therefore ncu will fail to land those PRs. Removing Lite-CI checks fix the issue and also reduces complexity. Fix: nodejs/node-core-utils#466
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We should probably remove checks for Lite-CI since we don't use it anymore.
The text was updated successfully, but these errors were encountered: