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

decouple analysis so it doesn't use a users development linux clone #2

Open
matthew-l-weber opened this issue Aug 14, 2024 · 3 comments

Comments

@matthew-l-weber
Copy link
Collaborator

Don't suggest to the user to use a development clone and leave the working folder the scripts use just for this workflow.

https://github.com/elisa-tech/delta-kernel/pull/1/files#r1693716744

Need to better describe the use cases the script is trying to meet.

  • CICD reports of tracking an upgrade's scope?
  • Person analysis to understand estimation
  • Reports to attach and reference in tickets to do change analysis
  • ?
@matthew-l-weber
Copy link
Collaborator Author

@matthew-l-weber
Copy link
Collaborator Author

#1 (comment)

@matthew-l-weber
Copy link
Collaborator Author

The initial #3 did strip out the second clone of the local copy since the tool isn't going to be part of a linux repo directly. Still need to update notes so it is clear that the tool should setup it's own working copies for analysis.

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

No branches or pull requests

1 participant