Skip to content
This repository has been archived by the owner on Feb 6, 2025. It is now read-only.

Add specific branch for aave use case #35

Open
Seth-Schmidt opened this issue Jan 20, 2024 · 0 comments
Open

Add specific branch for aave use case #35

Seth-Schmidt opened this issue Jan 20, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@Seth-Schmidt
Copy link

Seth-Schmidt commented Jan 20, 2024

Is your feature request related to a problem?
The aave use case codebase does not have an aave specific branch for Powerloom:deploy.

Describe the solution you'd like
A deploy branch for aave should be created to keep any necessary aave specific changes separate from other use cases.

Describe alternatives you've considered
Aave specific code changes could be pushed to the main branch, but it would be cleaner and easier to maintain by keeping a separate branch.

@Seth-Schmidt Seth-Schmidt added the enhancement New feature or request label Jan 20, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant