You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I had searched in the issues and found no similar issues.
What happened
When branches are deleted in github, the lake.refs table is not updated to either A: mark the branch as deleted, or B: the branch is deleted from the table.
This causes problems when trying to detect stale branches, because it includes branches that have already been deleted/tidied up in github.
What do you expect to happen
Either:
Mark the branch as deleted in the lake.refs table
Remove the branch from the lake.refs table
How to reproduce
Create a repository
Push an additional branch to the repository
Scrap the repository
Check the lake.refs table for the repo + branches
Delete the branch in the github UI
Scrape the repository
Check the lake.refs table for the branch - it should still exist.
Hey @cypher7682! 👋 I'm here to help you with any bugs, questions, or contributions you have for the project. I'll assist you while we wait for a human maintainer.
The issue you're encountering is related to the lake.refs table not being updated to reflect branch deletions from GitHub. Currently, there is no field in the lake.refs table specifically designed to mark a branch as deleted [1]. This means that when a branch is deleted in GitHub, it is not automatically marked or removed in the lake.refs table during a repository scrape.
To address this, you might consider implementing a mechanism to either mark branches as deleted or remove them from the table when they are deleted in GitHub. This would help in accurately detecting stale branches by excluding those that have been deleted.
Search before asking
What happened
When branches are deleted in github, the
lake.refs
table is not updated to either A: mark the branch as deleted, or B: the branch is deleted from the table.This causes problems when trying to detect stale branches, because it includes branches that have already been deleted/tidied up in github.
What do you expect to happen
Either:
lake.refs
tablelake.refs
tableHow to reproduce
lake.refs
table for the repo + brancheslake.refs
table for the branch - it should still exist.Anything else
No response
Version
devlake-1.0.2-beta1
Are you willing to submit PR?
Code of Conduct
The text was updated successfully, but these errors were encountered: