-
Notifications
You must be signed in to change notification settings - Fork 0
use {pacta.portfolio.utils} #168
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
Conversation
|
very excited for this. |
|
Docker image from this PR created |
|
Docker image from this PR created |
| uses: actions/checkout@v3 | ||
| with: | ||
| repository: RMI-PACTA/pacta.portfolio.utils | ||
| token: ${{ secrets.GITHUB_TOKEN }} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does this need a token? Isn't the repo public?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
will re-visit this later
jdhoffa
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
|
Docker image from this PR created |
I extracted all the utility functions that are used across web tool scripts 1-3 into a separate package. I think this will...
The most interesting/dramatic effect here is that web tool script 3 no longer needs pacta.portfolio.analysis because pacta.portfolio.utils has all the utility functions it needs. (Likewise, eventually web tool script 1 will need pacta.portfolio.audit and not pacta.portfolio.analysis).
Once this is merged, we should remove all the utility functions from pacta.portfolio.analysis. If we do things in this order, we avoid breaking anything temporarily. https://github.com/RMI-PACTA/pacta.portfolio.analysis/issues/242