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.

Sign up for GitHub

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

Jump to bottom

qa(js): when commit ID is non-existent for changedFiles #111

Open
jjangga0214 opened this issue May 26, 2023 · 0 comments
Open

qa(js): when commit ID is non-existent for changedFiles #111

jjangga0214 opened this issue May 26, 2023 · 0 comments

Comments

@jjangga0214
Copy link
Owner

jjangga0214 commented May 26, 2023 •
edited
Loading

There're some possible scenarios.

  • fetch-depth is too shallow
  • commit ID is amended or rebased
@jjangga0214 jjangga0214 changed the title qa(js): when commit ID is non-existent qa(js): when commit ID is non-existent for changedFiles May 26, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@jjangga0214