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

RSP Codebase relationship with Eliza repository #284

Open
ArsalonAmini2024 opened this issue Jan 23, 2025 · 1 comment
Open

RSP Codebase relationship with Eliza repository #284

ArsalonAmini2024 opened this issue Jan 23, 2025 · 1 comment
Assignees

Comments

@ArsalonAmini2024
Copy link
Collaborator

Arsalon Comment -

  • Do we pull new features from Eliza often? how often? what features? will they be compatible with our repo? Do we need to change our approach to ensure compatibility with Eliza pulls?
  • Do we build our own RS features and from time to time share some functionality with the Eliza (Open source) community? How to do that in terms of repo compatibility?
  • Our repo is forked and behind Eliza by a bunch, is it still compatible or did we introduce breaking changes, etc.

Caner Comment -

do we pull new features from Eliza often? how often? what features? will they be compatible with our repo? Do we need to change our approach to ensure compatibility with Eliza pulls?

  • yes we pull the latest changes from the develop branch to our sa-eliza repo every 5 minutes

Do we build our own RS features and from time to time share some functionality with the Eliza (Open source) community? How to do that in terms of repo compatibility?

  • that’s correct, depending on the features we decide to share it with the broader community or keep them in sa-eliza, for example coinbase plugin was merged into the upstream repo while github plugins and client are kept within our sa-eliza repo.

Our repo is forked and behind Eliza by a bunch, is it still compatible or did we introduce breaking changes, etc.

  • nope we are up to date with the upstream repo branches

Okay so the flow is then "feature-specific-branch" get's pull requested into "dev branch" and then "dev branch" after doing QA/testing gets merged into "main" branch for RS. And before a feature-specific-branch is created it should be created off the "dev branch"

  • what's the relationship between the dev branch and the main branch in the RS repo?
@ArsalonAmini2024 ArsalonAmini2024 changed the title RS relationship with Eliza repository RSP Codebase relationship with Eliza repository Jan 23, 2025
@ArsalonAmini2024
Copy link
Collaborator Author

Hi @monilpat this was something we talked about before. I think you and the devs already discussed this and have a solution in place. Can you comment that solution or document it into GDRIVE and then link it here + close this issue with a comment?

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

2 participants